CVE-2005-0518: eXeem 0.21 stores sensitive information such as passwords in plaintext in the Exeem registry key, which allows
CVE-2005-0518 is a low-severity flaw (CVSS 2.1) affecting exeem. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
eXeem 0.21 stores sensitive information such as passwords in plaintext in the Exeem registry key, which allows local users to gain privileges via the proxy_user and proxy_password values.
Why this priority
- Public exploit reference
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 2.1 (Low) |
| EPSS exploit chance | 0.7% (top 48%) |
| CISA exploited list | No |
| Published | 2005-02-23 |
| Last modified | 2026-06-16 |
Last updated 2026-06-16 · 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
Public exploits and detection
Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.
- Exploit-DB: eXeem 0.21 - Local Password Disclosure
- Exploit-DB: eXeem 0.21 - Local Password Disclosure (ASM)
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-2005-0518?
exeem: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2005-0518 being exploited?
CVE-2005-0518 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-2005-0518 affect?
CVE-2005-0518 affects exeem. Severity is low (CVSS 2.1). eXeem 0.21 stores sensitive information such as passwords in plaintext in the Exeem registry key, which allows local users to gain privileges via the proxy_user and proxy_password values.
How urgent is CVE-2005-0518?
Priority 25/100. Public exploit reference