CVE-2025-12833

GeoDirectory – WP Business Directory Plugin and Classified Listings Directory <= 2.8.139 - Missing Authorization to Authenticated (Author+) Arbitrary Image Attachment

2025-11-11 00:00
DityaRA

Strategic Overview

Status
Patched in 2.8.140
Affected Plugin
GeoDirectory – WP Business Directory Plugin and Classified Listings Directory
Affected Version
<= 2.8.139
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2025-12833
View all GeoDirectory – WP Business Directory Plugin and Classified Listings Directory vulnerabilities

At a glance

CVE-2025-12833 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the GeoDirectory WordPress plugin, affecting versions <= 2.8.139. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 2.8.140; sites on affected versions should update now. Disclosed November 2025, reported by DityaRA.

Vulnerability Overview

The GeoDirectory – WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.8.139 via the 'post_attachment_upload' function due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with author-level access and above, to attach arbitrary image files to arbitrary places.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

GeoDirectory <= 2.8.139 carries this weakness at post_attachment_upload, and reaching it takes an account at Author level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For GeoDirectory the fix is 2.8.140: builds <= 2.8.139 are affected, anything from 2.8.140 onward is not.

Remediation

Update to version 2.8.140, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: GeoDirectory 2.8.140 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-12833https://www.wordfence.com/threat-intel/vulnerabilities/id/408f0c2a-ef3c-4592-8722-d56afce92e24https://nvd.nist.gov/vuln/detail/CVE-2025-12833

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C