Store LocatorWordPress extension · Agilelogix
CVE-2023-4151
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 · uneditedThe Store Locator WordPress plugin before 1.4.13 does not sanitise and escape an invalid nonce before outputting it back in an AJAX response, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin
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 WordPress plugin before version 1.4.13 fails to sanitise and escape an invalid nonce value received in an AJAX request before reflecting it back in the AJAX response. This allows injection of malicious JavaScript code via the nonce parameter, which executes in the browser of admin users who trigger the AJAX request.
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 LocatorWordPress extension
< 1.4.13CVSS 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.
-
Check the Store Locator plugin versionIn WordPress admin, go to Plugins > Installed Plugins and look for 'Store Locator' or 'Agilelogix Store Locator' in the list. The version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file (usually store-locator.php or similar) for the 'Version' header in the plugin comment block.Affected if The displayed version is below 1.4.13 (for example, 1.4.12, 1.4.10, etc.)
-
Identify the plugin's AJAX endpointExamine the plugin PHP files for registered AJAX handlers using add_action('wp_ajax_...') or add_action('wp_ajax_nopriv_...'). Look for files that handle nonce verification and return the nonce value back in the response.Affected if The plugin registers AJAX handlers that return the nonce parameter in the response without sanitization.
-
Check for injected scripts in AJAX responsesTrigger the affected AJAX request (typically found in the plugin JavaScript files) with a malicious nonce parameter value containing script tags, such as <script>alert(1)</script>. Inspect the raw AJAX response to see if the script tags are reflected as-is without encoding.Affected if The AJAX response reflects the malicious nonce value exactly as sent, without HTML entity encoding, allowing script execution in an admin browser.
If the installed Store Locator plugin version is below 1.4.13 and the AJAX functionality that returns the nonce in the response is accessible, the environment is affected by this stored XSS vulnerability.
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.
dbcve · scoped1.4.13
Update the Store Locator plugin to version 1.4.13 or later, which includes proper sanitisation and escaping of the nonce parameter before it is output in the AJAX response.
1.4.13
- Backup your WordPress site before making any changes
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'Store Locator' plugin in the list
- Check if the current version is below 1.4.13
- If vulnerable, click 'Update Now' to upgrade to version 1.4.13 or latest available version
- Alternatively, you can update via WP-CLI: wp plugin update store-locator --version=1.4.13
- After updating, verify the new version number reflects 1.4.13 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Store Locator
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-4151 — 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-4151 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