Wp Multi Store LocatorWordPress extension · Wpexperts
CVE-2025-24680
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 · uneditedImproper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) vulnerability in WPExperts.io WP Multistore Locator wp-multi-store-locator allows Reflected XSS.This issue affects WP Multistore Locator: from n/a through <= 2.4.7.
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 confidenceReflected XSS vulnerability in the WP Multistore Locator WordPress plugin (versions <= 2.4.7) allows attackers to inject malicious scripts via unsanitized user input that gets reflected back in the web page. The vulnerability stems from improper neutralization of script-related HTML tags in HTTP parameters.
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
Wp Multi Store LocatorWordPress extension
< 2.5.1CVSS 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 installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins > locate 'Wpexperts Wp Multi Store Locator' and read the version number from the plugin description. Alternatively, check the plugin's main PHP file header for 'Version:' comment.Affected if The installed version is 2.4.7 or lower (any version before 2.5.1)
-
Identify if the plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and verify whether the 'Wpexperts Wp Multi Store Locator' plugin is activated.Affected if The plugin is activated and the version is vulnerable
-
Check for frontend locator functionality exposureVisit the site frontend and look for any store locator shortcode or page (commonly /store-locator/ or using [wpsl_] shortcode). Try submitting a search query with a test parameter to observe if user input is reflected in the response.Affected if The store locator functionality is publicly accessible and user input appears unsanitized in the page output
-
Review HTTP response for unsanitized parametersUse browser developer tools or a proxy to capture requests to the locator endpoint. Submit a request with a parameter value containing a benign test string like '<script>alert(1)</script>' and examine if this string is reflected unmodified in the HTML response.Affected if The submitted parameter value is reflected back in the HTML without encoding or sanitization
A user is affected if the Wpexperts Wp Multi Store Locator plugin version is 2.4.7 or lower and the store locator functionality is active and accessible on the site, allowing unsanitized user input to be reflected in the page.
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 · scoped2.5.1
Apply input validation and output encoding using WordPress escaping functions (esc_html, esc_attr, esc_url) on all user-supplied parameters before rendering in HTML context. Update the plugin to the latest patched version when available.
WP Multi Store Locator version 2.5.1
- 1. Back up your WordPress site and database before making any changes
- 2. Navigate to the WordPress admin dashboard
- 3. Go to Plugins > All Plugins
- 4. Find 'WP Multi Store Locator' in the plugins list
- 5. Click 'Update now' if an update is available, or manually upload version 2.5.1 via Plugins > Add New > Upload Plugin
- 6. Verify the plugin is updated to version 2.5.1 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wp Multi Store Locator
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24680 — 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-2025-24680 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