WordPress Store Locator plugin <= 1.4.5 - Cross-Site Scripting (XSS) via Cross-Site Request Forgery (CSRF) vulnerability

published 2022-11-18 3y ago modified 2026-06-17 4mo ago also EUVD-2022-44806

cvss: 6.1; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 17%
public exploits: 0; none known

Cross-Site Scripting (XSS) via Cross-Site Request Forgery (CSRF) vulnerability in Store Locator plugin <= 1.4.5 on WordPress.

Patch / fix

fixed in 1

agilelogix store_locator 1.4.6

Is CVE-2022-41615 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	6.1	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD	3.1	6.1	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Affected products

AGILELOGIX Store Locator WordPress (WordPress plugin)

Classification

Weakness

CWE-352 Cross-Site Request Forgery
CWE-79 Improper Neutralization of Input During Web Page Generation

Technology feeds

WordPress rss critical rss

References

patchstack.com /database/vulnerability/agile-store-locator/wordpress-store-locator-plugin-1-4-5-cross-site-scripting-xss-via-
third-party-advisory
wordpress.org /plugins/agile-store-locator/
third-party-advisory

Sources

CVE List CVE-2022-41615
NVD CVE-2022-41615

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.