CVE-2022-2375: The WP Sticky Button WordPress plugin before 1.4.1 does not have authorisation and CSRF checks when saving its

Q: How do I fix CVE-2022-2375?

wp sticky button: upgrade to 1.4.1. Exact commands for each OS are on this page.

Q: Is CVE-2022-2375 being exploited?

CVE-2022-2375 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-2375 affect?

CVE-2022-2375 affects wp sticky button. Severity is medium (CVSS 5.4). 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

Q: How urgent is CVE-2022-2375?

Priority 31/100. Public exploit reference

Routine

MEDIUM 5.4UPGRADE

CVE-2022-2375 is a medium-severity flaw (CVSS 5.4) affecting wp sticky button. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	5.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.4% (top 70%)
CISA exploited list	No
Weakness	CWE-79, CWE-352
Published	2022-08-22
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: okapitech

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-08-22 15:15 UTCPublished CVE record published
2026-06-17 04:41 UTCUpdated Record last modified

okapitech wp sticky button UPGRADE

Affected: < 1.4.1

Fixed in: 1.4.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wp-sticky-button || rpm -q wp-sticky-button || wp-sticky-button --version

2. UPGRADE to 1.4.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wp-sticky-button

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wp-sticky-button

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-2375?

wp sticky button: upgrade to 1.4.1. Exact commands for each OS are on this page.

Is CVE-2022-2375 being exploited?

CVE-2022-2375 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-2375 affect?

CVE-2022-2375 affects wp sticky button. Severity is medium (CVSS 5.4). 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

How urgent is CVE-2022-2375?

Priority 31/100. Public exploit reference

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs