Store Locator PlusWordPress extension · Storelocatorplus
CVE-2024-43258
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 · uneditedExposure of Sensitive Information to an Unauthorized Actor vulnerability in Store Locator Plus.This issue affects Store Locator Plus: from n/a through 2311.17.01.
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 · moderate confidenceThis is an information disclosure vulnerability in the Store Locator Plus WordPress plugin affecting versions up to 2311.17.01. The flaw allows unauthenticated actors to access sensitive information that should be protected, likely through an unprotected endpoint or insufficient access controls.
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
Store Locator PlusWordPress extension
<= 2311.17.01CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Check installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins > Store Locator Plus and note the version number displayed. Alternatively, check the plugin's main PHP file header or version.php for the version constant.Affected if The installed version is 2311.17.01 or lower.
-
Inspect REST API endpoint exposureAccess common plugin API routes such as /wp-json/slp/, /wp-admin/admin-ajax.php?action=slp_, or any custom endpoints the plugin registers. Use a browser or curl to request these endpoints without authentication.Affected if The endpoints return sensitive location data, user information, or database contents without requiring authentication.
-
Review AJAX action access controlsExamine the plugin's AJAX handlers by inspecting its PHP files for add_action('wp_ajax_...) calls. Test each action with unauthenticated requests using a tool like curl or Burp Suite.Affected if Any AJAX actions respond to unauthenticated requests and return sensitive information such as database records, API keys, or user data.
-
Check for unprotected data export featuresLook for any plugin pages or endpoints that may expose data exports, CSV generation, or bulk data retrieval. Attempt to access these without logging in.Affected if The feature returns location data, admin settings, or other sensitive information without authentication.
A user is affected if they run Store Locator Plus version 2311.17.01 or lower AND have any API endpoint, AJAX action, or data export feature accessible without authentication.
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 dataUpgrade to a patched version of Store Locator Plus beyond 2311.17.01. Review plugin settings and disable any exposed API endpoints until the patch is applied.
Fix this in Store Locator Plus
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43258 — 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-2024-43258 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