CVE-2024-6330 json
GEO my WordPress < 4.4.0.2 - Unauthenticated RCE via LFI
published 2y ago modified 4mo ago also EUVD-2024-47444
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
The GEO my WP WordPress plugin before 4.5.0.2 does not prevent unauthenticated attackers from including arbitrary files in PHP's execution context, which leads to Remote Code Execution.
Patch / fix
- Unknown GEO my WP 4.5.0.2
- geo_my_wp geo_my_wp 4.5.0.2
Is CVE-2024-6330 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 2y ago
Exploit prediction
2.14% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/95b532e0-1ffb-421e-b9c0-de03f89491d7/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Unknown GEO my WP
- geo_my_wp geo_my_wp
Classification
- Technology feeds
References
-
wpscan.com
/vulnerability/95b532e0-1ffb-421e-b9c0-de03f89491d7/
exploit, vdb-entry, technical-description, third-party-advisory
Sources
- CVE List CVE-2024-6330
- NVD CVE-2024-6330
Fencer Intel 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.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.