CVE-2024-3591: The Geo Controller WordPress plugin before 8.6.5 unserializes user input via some of its AJAX actions and REST

Q: How do I fix CVE-2024-3591?

geo controller: upgrade to 8.6.5. Exact commands for each OS are on this page.

Q: Is CVE-2024-3591 being exploited?

CVE-2024-3591 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-3591 affect?

CVE-2024-3591 affects geo controller. Severity is medium (CVSS 6.5). The Geo Controller WordPress plugin before 8.6.5 unserializes user input via some of its AJAX actions and REST API routes, which could allow unauthenticated users to perform PHP Object Injection when a suitable gadget is present on the blog

Q: How urgent is CVE-2024-3591?

Priority 43/100. Public exploit reference; Remotely exploitable, no login, no user action

This week

MEDIUM 6.5REMOTEUPGRADE

CVE-2024-3591 is a medium-severity flaw (CVSS 6.5) affecting geo controller. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Geo Controller WordPress plugin before 8.6.5 unserializes user input via some of its AJAX actions and REST API routes, which could allow unauthenticated users to perform PHP Object Injection when a suitable gadget is present on the blog.

Why this priority

Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.5% (top 58%)
CISA exploited list	No
Weakness	CWE-502
Published	2024-05-01
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: infinitumform

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-05-01 06:15 UTCPublished CVE record published
2026-06-17 07:44 UTCUpdated Record last modified

infinitumform geo controller UPGRADE

Affected: < 8.6.5

Fixed in: 8.6.5

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy geo-controller || rpm -q geo-controller || geo-controller --version

2. UPGRADE to 8.6.5 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade geo-controller

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade geo-controller

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
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-2024-3591?

geo controller: upgrade to 8.6.5. Exact commands for each OS are on this page.

Is CVE-2024-3591 being exploited?

CVE-2024-3591 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-2024-3591 affect?

CVE-2024-3591 affects geo controller. Severity is medium (CVSS 6.5). The Geo Controller WordPress plugin before 8.6.5 unserializes user input via some of its AJAX actions and REST API routes, which could allow unauthenticated users to perform PHP Object Injection when a suitable gadget is present on the blog

How urgent is CVE-2024-3591?

Priority 43/100. Public exploit reference; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities · PHP vulnerabilities

Related CVEs

CVE-2024-7381 MEDIUM 5.3 UPGRADE The Geo Controller plugin for WordPress is vulnerable to unauthorized shortcode execution due to missing autho
CVE-2024-7380 MEDIUM 4.3 UPGRADE The Geo Controller plugin for WordPress is vulnerable to unauthorized menu creation/deletion due to missing ca

References

← Back to latest CVEs