CVE-2024-9422· NVD / CVE Program· CNA WPScan

GEO My WordPress < 4.5 - Admin+ Arbitrary File Upload

The GEO my WP WordPress plugin before 4.5, gmw-premium-settings WordPress plugin before 3.1 does not sufficiently validate files to be uploaded, which could allow attackers to upload arbitrary files such as PHP on the server.

MediumCVSS 6.6 · v3.1—No exploit Fix available

File upload

Published: Nov 22, 2024
Updated: Jun 17, 2026
EPSS: 0.8% · 53th percentile
CWE: CWE-434

Follow this CVE

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 26 / 40 · 6.6 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.8%

CISA SSVC decision

Exploitation: proof of concept
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

Vendor	Product	CPE
geomywp	geo my wordpress	cpe:2.3:a:geomywp:geo_my_wordpress
geomywp	geo my wordpress premium settings	cpe:2.3:a:geomywp:geo_my_wordpress_premium_settings

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

geomywp geo my wordpressbefore 4.5
geomywp geo my wordpress premium settingsbefore 3.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (WPScan). Independent of NVD's CPE analysis and usually ahead of it.

Unknown GEO my WP
- 4.0 and later · before 4.5affected · semver
Unknown gmw-premium-settings
- before 3.1affected · semver

Same product

geomywp: all records

Other highest-scoring records for the same primary product.

CVE-2024-6330GEO my WordPress < 4.4.0.2 - Unauthenticated RCE via LFI
40Plan
CVE-2023-52134WordPress GEO my WordPress Plugin <= 4.0.2 is vulnerable to SQL Injection
28Monitor
CVE-2023-5467GEO my WordPress <= 4.0 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode
21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Unknown GEO my WP	4.5	Vendor (CNA)
Unknown gmw-premium-settings	3.1	Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Michael Dyrnafinder
WPScancoordinator

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).