{"id":"CVE-2025-52203","url":"https://www.cyber-defence.io/tools/cve/CVE-2025-52203","generatedAt":"2026-10-28T05:59:41.154Z","title":"A stored cross-site scripting (XSS) vulnerability exists in DevaslanPHP project-management v1.2.4.","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.","published":"2025-07-31T16:15:31.000Z","lastModified":"2026-06-17T09:36:19.000Z","status":"Analyzed","sourceIdentifier":"cve@mitre.org","cvss":{"version":"3.1","score":7.6,"severity":"HIGH","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:H"},"cwe":["CWE-79"],"affected":["devaslanphp/project management"],"epss":{"score":0.00335,"percentile":0.26714,"date":"2026-10-27","history":[]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"high","text":"High impact if exploited, but EPSS currently rates exploitation as unlikely (0.34%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit."},"changes":[],"references":[{"url":"https://github.com/devaslanphp/project-management/releases","tags":["Release Notes"],"source":"cve@mitre.org"},{"url":"https://github.com/ischyr/research-and-development/tree/main/CVE-2025-52203","tags":["Exploit"],"source":"cve@mitre.org"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2025-52203","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}