CVE-2025-12282: code-projects Client Details System · Cross Site Scripting
Affects code-projects Client Details SystemSource CVE Database V5
Not known to be exploited · CVSS 4.8 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 27 Oct 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubhellonewbie/tutorialpkg:github/hellonewbie/tutorialOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Monitor vendor channels closely for official patches or updates addressing CVE-2025-12282 and apply them promptly upon release. 2. Implement strict input validation and output encoding on all user-supplied data within the /admin/manage-users.php interface to prevent script injection. 3. Restrict administrative interface access to trusted networks or VPNs, minimizing exposure to remote attackers. 4. Employ multi-factor authentication (MFA) for all administrative accounts to reduce the risk of credential compromise. 5. Conduct regular security audits and penetration testing focused on administrative modules to detect similar vulnerabilities. 6. Use Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in the browser context. 7. Educate administrative users about the risks of interacting with suspicious links or inputs that could trigger XSS payloads. 8. Implement web application firewalls (WAF) with rules tuned to detect and block XSS attack patterns targeting the affected endpoints. These measures, combined, reduce the likelihood and impact of exploitation beyond generic advice.
Description
A vulnerability was identified in code-projects Client Details System 1.0. The affected element is an unknown function of the file /admin/manage-users.php. The manipulation leads to cross site scripting. The attack can be initiated remotely. The exploit is publicly available and might be used.