CVE-2022-1750: The Sticky Popup plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘ popup_title' para

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

sticky popup: upgrade to newer than 1.2. Exact commands for each OS are on this page.

Q: Is CVE-2022-1750 being exploited?

CVE-2022-1750 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-1750 affect?

CVE-2022-1750 affects sticky popup. Severity is medium (CVSS 5.5). The Sticky Popup plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘ popup_title' parameter in versions up to, and including, 1.2 due to insufficient input sanitization and output escaping. This makes it possible for

Q: How urgent is CVE-2022-1750?

Priority 31/100. No elevated risk signals yet.

Routine

MEDIUM 5.5UPGRADE

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

The Sticky Popup plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘ popup_title' parameter in versions up to, and including, 1.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with admin level capabilities and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This issue mostly affects sites where unf

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	None
EPSS exploit chance	0.6% (top 54%)
CISA exploited list	No
Weakness	CWE-79
Published	2022-06-13
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: sticky popup project

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

Am I affected?

Timeline

2022-06-13 14:15 UTCPublished CVE record published
2026-06-17 04:23 UTCUpdated Record last modified

sticky popup project sticky popup UPGRADE

Affected: <= 1.2

Fixed in: newer than 1.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy sticky-popup || rpm -q sticky-popup || sticky-popup --version

2. UPGRADE to newer than 1.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade sticky-popup

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade sticky-popup

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-1750?

sticky popup: upgrade to newer than 1.2. Exact commands for each OS are on this page.

Is CVE-2022-1750 being exploited?

CVE-2022-1750 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-1750 affect?

CVE-2022-1750 affects sticky popup. Severity is medium (CVSS 5.5). The Sticky Popup plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘ popup_title' parameter in versions up to, and including, 1.2 due to insufficient input sanitization and output escaping. This makes it possible for

How urgent is CVE-2022-1750?

Priority 31/100. No elevated risk signals yet.

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs