Store Locator PlusWordPress extension · De Baat
CVE-2021-24290
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 · uneditedThere are several endpoints in the Store Locator Plus for WordPress plugin through 5.5.15 that could allow unauthenticated attackers the ability to inject malicious JavaScript into pages.
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 confidenceThe Store Locator Plus WordPress plugin versions up to 5.5.15 contains multiple endpoints that fail to properly sanitize user input, allowing unauthenticated attackers to inject malicious JavaScript code that gets stored and executed when page visitors access the affected pages.
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
<= 5.5.15CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Identify plugin installation and versionNavigate to WordPress admin > Plugins > Installed Plugins. Locate 'De Baat Store Locator Plus' and note the version number displayed. Compare this against the affected version range (5.5.15 and below).Affected if The plugin version is 5.5.15 or lower.
-
Confirm plugin is activeIn the same Plugins screen, verify whether 'De Baat Store Locator Plus' shows as 'Active'. The vulnerability requires the plugin to be running to expose its vulnerable endpoints.Affected if The plugin is installed and currently active.
-
Check for the store locator shortcode or widget usageGo to Pages or Posts in WordPress admin. Search for pages containing the store locator shortcode (commonly [store_locator_plus] or similar) or check Appearance > Widgets for an active Store Locator widget.Affected if The store locator functionality is published on any live page or post, as this creates the attack surface where stored XSS can execute when visitors access those pages.
-
Inspect plugin database for injected scriptsAccess the WordPress database via phpMyAdmin or wp cli. Examine the plugin's store location tables (typically wp_slp_store) for any records containing script tags, iframe tags, or javascript: URIs in address/name fields.Affected if Any store location records contain unexpected HTML script tags or JavaScript event handlers in data fields.
You are affected if De Baat Store Locator Plus version 5.5.15 or lower is installed and active, with the locator functionality exposed on your site.
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 dataUpdate to version 5.5.16 or later which contains the security fix, or remove the plugin if update is unavailable.
Fix this in Store Locator Plus
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-24290 — 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-2021-24290 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