Store Locator WordPress <= 1.4.5 - Cross-Site Request Forgery to Cross-Site Scripting
Strategic Overview
- Status
- Patched in 1.4.6
- Affected Plugin
- Agile Store Locator
- Affected Version
<= 1.4.5- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2022-41615
At a glance
CVE-2022-41615 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Agile Store Locator WordPress plugin, affecting versions <= 1.4.5. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.4.6; sites on affected versions should update now. Disclosed September 2022, reported by Nguy Minh Tuan.
Vulnerability Overview
The Store Locator WordPress plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.4.5. This is due to missing or incorrect nonce validation on the handle_request function. This makes it possible for unauthenticated attackers to modify the plugin's settings and inject malicious web scripts, via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in Agile Store Locator <= 1.4.5 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Agile Store Locator the fix is 1.4.6: builds <= 1.4.5 are affected, anything from 1.4.6 onward is not.
Remediation
Update to version 1.4.6, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Agile Store Locator: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Agile Store Locator 1.4.6 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Agile Store Locator
- 7.2CVE-2025-49329: Store Locator WordPress <= 1.5.2 Arbitrary File Upload
CVE-2025-49329 - 6.6CVE-2023-50885: Store Locator WordPress Directory Traversal
CVE-2023-50885 - 6.5CVE-2025-67516: Store Locator WordPress <= 1.6.2 SQL Injection
CVE-2025-67516 - 6.4CVE-2022-4832: Store Locator WordPress <= 1.4.8 Stored XSS
CVE-2022-4832 - 6.1CVE-2023-4151: Store Locator WordPress <= 1.4.12 Reflected XSS
CVE-2023-4151 - 4.9CVE-2026-9062: Agile Store Locator <= 1.6.8 Arbitrary File Read
CVE-2026-9062 - 4.9CVE-2025-49328: Store Locator WordPress <= 1.5.1 SQL Injection
CVE-2025-49328 - 4.4CVE-2026-9060: Store Locator WordPress < 1.6.6 Stored XSS
CVE-2026-9060
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C