CVE-2023-3666: The Sticky Side Buttons WordPress plugin before 2.0.0 does not sanitise and escape some of its settings, which

Q: How do I fix CVE-2023-3666?

sticky side buttons: upgrade to 2.0.0. Exact commands for each OS are on this page.

Q: Is CVE-2023-3666 being exploited?

CVE-2023-3666 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-2023-3666 affect?

CVE-2023-3666 affects sticky side buttons. Severity is low (CVSS 3.3). The Sticky Side Buttons WordPress plugin before 2.0.0 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capab

Q: How urgent is CVE-2023-3666?

Priority 19/100. Public exploit reference

Routine

LOW 3.3UPGRADE

CVE-2023-3666 is a low-severity flaw (CVSS 3.3) affecting sticky side buttons. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Sticky Side Buttons WordPress plugin before 2.0.0 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup)

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	3.3 (Low)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	High
User interaction	None
EPSS exploit chance	0.2% (top 89%)
CISA exploited list	No
Weakness	CWE-79
Published	2025-09-03
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: maevelander

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

Am I affected?

Timeline

2025-09-03 06:15 UTCPublished CVE record published
2026-06-17 06:14 UTCUpdated Record last modified

maevelander sticky side buttons UPGRADE

Affected: < 2.0.0

Fixed in: 2.0.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy sticky-side-buttons || rpm -q sticky-side-buttons || sticky-side-buttons --version

2. UPGRADE to 2.0.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade sticky-side-buttons

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade sticky-side-buttons

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-2023-3666?

sticky side buttons: upgrade to 2.0.0. Exact commands for each OS are on this page.

Is CVE-2023-3666 being exploited?

CVE-2023-3666 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-2023-3666 affect?

CVE-2023-3666 affects sticky side buttons. Severity is low (CVSS 3.3). The Sticky Side Buttons WordPress plugin before 2.0.0 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capab

How urgent is CVE-2023-3666?

Priority 19/100. Public exploit reference

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs