CVE-2025-52203: n/a
Source CVE Database V5
Not known to be exploited · CVSS 7.6 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:HExploitation evidence
Disclosed: evidence found.
CVE published 31 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
AI-suggested
To mitigate this vulnerability, organizations should immediately apply any available patches or updates from the vendor once released. In the absence of a patch, implement strict input validation and output encoding on the Ticket Name field to neutralize malicious scripts. Employ a web application firewall (WAF) with rules designed to detect and block XSS payloads targeting the affected endpoint. Conduct regular security audits and code reviews focusing on input sanitization practices. Limit user privileges to reduce the risk of unauthorized script injection, ensuring only trusted users can create or modify tickets. Educate users about the risks of XSS and encourage reporting of suspicious behavior. Additionally, implement Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. Monitor logs for unusual activity related to ticket creation or dashboard access to detect potential exploitation attempts early.
Description
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 malicious script executes in the user's browser context.