LocatoraidWordPress extension · Plainware
CVE-2023-25709
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in Plainware Locatoraid Store Locator plugin <= 3.9.11 versions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCross-Site Request Forgery (CSRF) vulnerability in Plainware Locatoraid Store Locator plugin versions 3.9.11 and earlier allows attackers to induce authenticated administrators to perform unwanted state-changing actions (such as modifying store locations or plugin settings) via maliciously crafted requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
LocatoraidWordPress extension
<= 3.9.11CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed plugin versionLocate the plugin files in the web root (commonly in /wp-content/plugins/locatoraid/ or similar) and open the main PHP file (often named locatoraid.php or version.php) to read the version declaration. Alternatively, check the WordPress admin panel under Plugins > Installed Plugins to view the Locatoraid version.Affected if The installed version number is 3.9.11 or lower.
-
Verify presence of anti-CSRF tokens in admin formsNavigate to the plugin admin pages that handle store location management or plugin settings. View the HTML source of forms that modify data (add/edit store, save settings) and search for hidden input fields containing tokens (commonly named 'nonce', 'token', 'csrf', or '_wpnonce'). Also check if forms include 'wpnonce' or similar WordPress nonce fields.Affected if State-changing admin forms lack anti-CSRF token fields or the tokens are not validated server-side when the form is submitted.
-
Confirm Origin/Referer header validationIntercept a legitimate state-changing admin request (such as saving a store location) using a browser dev tool or proxy. Manually modify or remove the Origin and Referer headers in the request and resend it. Check if the server accepts or rejects the request.Affected if The server processes state-changing requests even when Origin/Referer headers are missing, tampered, or point to an unrelated domain.
-
Test for predictable action parametersUsing the browser dev tools or a request interceptor, observe the parameter names and values in state-changing admin forms (such as 'action', 'task', 'do', or 'submit'). Determine if these parameters follow a predictable or easily guessable pattern that could be replicated in a malicious request.Affected if State-changing actions rely solely on predictable parameters without requiring a unique, session-bound token.
The environment is affected if the installed Plainware Locatoraid version is 3.9.11 or earlier AND the plugin does not implement anti-CSRF tokens on state-changing admin operations.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement anti-CSRF tokens (synchronizer tokens) on all state-changing operations and validate Origin/Referer headers. If available, upgrade to a patched version > 3.9.11.
Fix this in Locatoraid
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25709 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-25709 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data