CVE-2026-5252
Received Received - Intake
Remote XSS in z-9527 Admin Message Create Endpoint

Publication date: 2026-04-01

Last updated on: 2026-04-29

Assigner: VulDB

Description
A security flaw has been discovered in z-9527 admin 1.0/2.0. Affected is an unknown function of the file /server/routes/message.js of the component Message Create Endpoint. Performing a manipulation results in cross site scripting. The attack can be initiated remotely. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-01
Last Modified
2026-04-29
Generated
2026-05-07
AI Q&A
2026-04-01
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Currently, no data is known.
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
CWE-94 The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2026-5252 is a stored Cross-Site Scripting (XSS) vulnerability found in the Z-9527 Admin software, specifically in the message board functionality. The issue exists because the message creation endpoint accepts user-supplied content without any sanitization or validation, stores it directly in the database, and later renders it on the frontend using React's dangerouslySetInnerHTML without escaping or sanitizing the content.

This allows an attacker to inject arbitrary JavaScript code into messages, which then executes in the browsers of users viewing the message board.

  • The backend message creation endpoint (/server/routes/message.js) inserts unsanitized user input directly into the database.
  • The frontend renders this content using dangerouslySetInnerHTML without sanitization, enabling script execution.

How can this vulnerability impact me? :

This vulnerability allows authenticated attackers to inject malicious JavaScript code into the message board, which executes in the browsers of other users.

  • Attackers can perform session hijacking by stealing session cookies.
  • Credential theft is possible through malicious scripts.
  • Unauthorized actions can be performed on behalf of victims, such as changing settings or sending messages.

Overall, this can lead to compromised user accounts, loss of data integrity, and reduced trust in the affected application.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by testing the message creation endpoint for stored Cross-Site Scripting (XSS) issues. Specifically, sending crafted payloads to the POST /message/create API endpoint and observing if the input is stored and later executed in the frontend without sanitization.

  • Use curl or similar tools to send a test message with a simple XSS payload, for example: curl -X POST -H "Content-Type: application/json" -d '{"content":"<img src=x onerror=alert(1)>"}' http://yourserver/message/create
  • After sending the payload, visit the message board page in a browser and check if the alert box appears, indicating execution of injected JavaScript.
  • Alternatively, use automated web vulnerability scanners that test for stored XSS vulnerabilities on the message creation endpoint.

What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include sanitizing and validating all user input on the server side before storing it in the database.

  • Implement HTML sanitization libraries such as DOMPurify to clean message content before database insertion.
  • Avoid using React's dangerouslySetInnerHTML for rendering user-generated content; use safe rendering methods instead.
  • Apply Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in the browser.
  • Validate input against a whitelist of allowed HTML tags and attributes to prevent malicious code injection.

How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability allows authenticated attackers to inject arbitrary JavaScript code into the message board, which executes in the browsers of users viewing the board. This can lead to session hijacking, credential theft, and unauthorized actions performed on behalf of victims.

Such security flaws can impact compliance with common standards and regulations like GDPR and HIPAA because they may lead to unauthorized access to personal or sensitive data, compromise user privacy, and violate requirements for protecting data integrity and confidentiality.

Specifically, the risk of credential theft and session hijacking could result in unauthorized disclosure or misuse of personal data, which is a violation of GDPR's data protection principles and HIPAA's safeguards for protected health information.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart