CVE-2007-4649 json
MicroWorld eScan Virus Control 9.0.722.1, Anti-Virus 9.0.722.1, and Internet Security 9.0.722.1 use weak permissions (Everyone:Full Control…
published 2007-08-31 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-4631
- cvss
- 7.2
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 59%
- public exploits
- 1
- Exploit-DB
Summary
MicroWorld eScan Virus Control 9.0.722.1, Anti-Virus 9.0.722.1, and Internet Security 9.0.722.1 use weak permissions (Everyone:Full Control) for their installation directory trees, which allows local users to gain privileges by replacing application files, as demonstrated by traysser.exe.
Timeline
- First public exploit (EDB-30546)
- Published
Exploit prediction
0.89% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-30546 Microworld eScan (Multiple Products) - Local Privilege Escalation local, 2007-08-30
- securityfocus.com http://www.securityfocus.com/bid/25493 referenced PoC, tagged "exploit" by a source, unverified
- lists.grok.org.uk http://lists.grok.org.uk/pipermail/full-disclosure/2007-August/065509.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
References
-
securityfocus.com
/bid/25493
vdb-entry, exploit
-
lists.grok.org.uk
/pipermail/full-disclosure/2007-August/065509.html
mailing-list, exploit
-
secunia.com
/advisories/26581
third-party-advisory, vendor-advisory
-
securityreason.com
/securityalert/3085
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/36367
vdb-entry
Sources
- CVE List CVE-2007-4649
- NVD CVE-2007-4649
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.