Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Search

GHSA-fc4p-p49v-r948

CriticalCVSS 9.9 / 10
Published Apr 1, 2026·Last modified Apr 6, 2026
Affected Components(0)

No affected components available

Description

Summary

A critical Stored Cross-Site Scripting (Stored XSS) vulnerability exists in the backend user management functionality. The application fails to properly sanitize user-controlled input before rendering it in the administrative interface, allowing attackers to inject persistent JavaScript code. This results in automatic execution whenever backend users access the affected page, enabling session hijacking, privilege escalation, and full administrative account compromise.


Details

The vulnerability resides in the backend user creation feature accessible via:

/backend/users

User-supplied input in the name and surname fields is stored without proper validation or sanitization. When this data is later rendered in the backend users listing page, it is injected directly into the HTML without output encoding.

Because of this, attackers can embed malicious JavaScript payloads that execute in the context of authenticated backend users.

This indicates missing contextual output escaping (e.g., HTML encoding) and insufficient input sanitization, leading to persistent script execution.

The vulnerability is particularly severe because:

  • The payload is stored in the database (persistent XSS).
  • The script executes automatically on page load.
  • The affected page appears to be an administrative/backend interface, increasing the risk of privilege escalation.

PoC

Steps to reproduce:

  1. Navigate to:
http://localhost:8080/backend/users
  1. Click Add New User.

  2. Create a new user.

  3. In the name and surname fields, insert the following payload:

adnan"><img src=1 onerror=alert(document.cookie)><<e>img src=1 onerror=alert(document.cookie)>
  1. Save the user.

  2. After saving, a popup displaying cookies will appear, demonstrating JavaScript execution.

  3. Revisit:

http://localhost:8080/backend/users
  1. The popup automatically triggers again, confirming that the malicious script is stored and executed persistently. <img width="1534" height="834" alt="image" src="https://github.com/user-attachments/assets/83f3d124-cf2e-472d-87cc-8c668ea81cba" />

Impact

Severity: Critical

This vulnerability enables:

  • Persistent execution of attacker-controlled JavaScript in privileged backend contexts.
  • Theft of session cookies, potentially leading to full account takeover.
  • Unauthorized actions performed on behalf of administrators (CSRF-like behavior via XSS).
  • Privilege escalation if a high-privilege user views the page.
  • Injection of keyloggers, credential harvesting scripts, or malicious redirects.
  • Full compromise of backend administrative functionality depending on role permissions.

Since the payload executes automatically without user interaction once stored, exploitation requires minimal effort and can impact all backend users.

Risk Scores
Base Score
9.9

The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker needs basic access or low-level privileges. No user interaction is needed for the attacker to exploit this vulnerability. The vulnerability can affect other systems as well, not just the initial system. There is a high impact on the confidentiality of the information. There is a high impact on the integrity of the data. There is a high impact on the availability of the system.

Threat Intelligence
9.1

Active exploitation in the wild has been confirmed. Immediate patching or mitigation is required.

EPSS
0.39%

The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.

Exploit
Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.

Checkout DevGuard