CVE-2022-2375 json
WP Sticky Button < 1.4.1 - Unauthenticated Arbitrary Settings Update to Stored XSS
published 2022-08-22 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-34642
- cvss
- 5.4
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 31%
- public exploits
- 0
- none known
Summary
The WP Sticky Button WordPress plugin before 1.4.1 does not have authorisation and CSRF checks when saving its settings, allowing unauthenticated users to update them. Furthermore, due to the lack of escaping in some of them, it could lead to Stored Cross-Site Scripting issues
Patch / fix
- okapitech wp_sticky_button 1.4.1
Exploit prediction
0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/caab1fca-cc6b-45bb-bd0d-f857edd8bb81 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
Affected products
- Unknown WP Sticky Button – Click to Chat
Classification
- Weakness
- Technology feeds
References
-
wpscan.com
/vulnerability/caab1fca-cc6b-45bb-bd0d-f857edd8bb81
exploit, third-party-advisory
Sources
- CVE List CVE-2022-2375
- NVD CVE-2022-2375
Fencer Vulns 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.