CVE-2025-52203: A stored cross-site scripting (XSS) vulnerability exists in DevaslanPHP project-management v1.2.4
CVE-2025-52203 is a high-severity flaw (CVSS 7.6) affecting project management. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
A stored cross-site scripting (XSS) vulnerability exists in DevaslanPHP project-management v1.2.4. The vulnerability resides in the Ticket Name field, which fails to properly sanitize user-supplied input. An authenticated attacker can inject malicious JavaScript payloads into this field, which are subsequently stored in the database. When a legitimate user logs in and is redirected to the Dashboard panel "automatically upon authentication the mal
Why this priority
- High severity
- Public exploit reference
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 7.6 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.3% (top 73%) |
| CISA exploited list | No |
| Weakness | CWE-79 |
| Published | 2025-07-31 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2025-52203?
project management: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2025-52203 being exploited?
CVE-2025-52203 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2025-52203 affect?
CVE-2025-52203 affects project management. Severity is high (CVSS 7.6). A stored cross-site scripting (XSS) vulnerability exists in DevaslanPHP project-management v1.2.4. The vulnerability resides in the Ticket Name field, which fails to properly sanitize user-supplied input. An authenticated attacker can injec
How urgent is CVE-2025-52203?
Priority 38/100. High severity; Public exploit reference