GEO my WordPress: PHP object injection
Unauthenticated PHP Object Injection in GEO my WordPress <= 4.5.5.3 versions. The export does not disclose the endpoint, input parameter, vulnerable function or detailed input-processing path. No additional exploit mechanics are inferred. Untrusted deserialization may create PHP objects; code execution requires a usable gadget chain and its prerequisites, neither of which is established by this record. The structured affected range is n/a through 4.5.5.3.
- Component
- GEO my WordPress
- Plugin slug
geo-my-wp- Affected
- n/a through 4.5.5.3
- Safe version
4.5.5.4- Published
- Oct 29, 2026
This CVE was published Oct 29, 2026 and is one of 12 known issues for this plugin.
Update, patch or deactivate.
Update to a supported release containing the confirmed fix: 4.5.5.4. Do not deserialize attacker-controlled input into PHP objects; enforce the intended authorization before processing it.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
Unauthenticated PHP Object Injection in GEO my WordPress <= 4.5.5.3 versions.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H