GeoDirectory – WP Business Directory Plugin and Classified Listings Directory <= 2.8.176 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 2.8.177
- Affected Version
<= 2.8.176- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2026-81271
At a glance
CVE-2026-81271 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the GeoDirectory WordPress plugin, affecting versions <= 2.8.176. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.8.177; sites on affected versions should update now. Disclosed August 2026, reported by Brian Willows.
Vulnerability Overview
The GeoDirectory – WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.8.176. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to perform an unauthorized action via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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 privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in GeoDirectory <= 2.8.176 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For GeoDirectory the fix is 2.8.177: builds <= 2.8.176 are affected, anything from 2.8.177 onward is not.
Remediation
Update to version 2.8.177, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to GeoDirectory: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: GeoDirectory 2.8.177 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in GeoDirectory – WP Business Directory Plugin and Classified Listings Directory
- 9.9CVE-2024-43145: GeoDirectory <= 2.3.61 SQL Injection
CVE-2024-43145 - 8.1CVE-2026-19091: GeoDirectory <= 2.8.169 Arbitrary File Deletion
CVE-2026-19091 - 7.5CVE-2026-54831: GeoDirectory SQL Injection
CVE-2026-54831 - 7.5CVE-2026-39512: GeoDirectory SQL Injection
CVE-2026-39512 - 7.5CVE-2024-13507: GeoDirectory SQL Injection
CVE-2024-13507 - 7.2CVE-2026-66604: GeoDirectory Stored XSS
CVE-2026-66604 - 7.2GeoDirectory <= 2.3.28 SQL Injection via orderby
- 7.2CVE-2023-0278: GeoDirectory <= 2.2.23 SQL Injection
CVE-2023-0278
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C