CVE-2022-0214: The Custom Popup Builder WordPress plugin before 1.3.1 autoload data from its popup on every pages, as such da

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

custom popup builder: upgrade to 1.3.1. Exact commands for each OS are on this page.

Q: Is CVE-2022-0214 being exploited?

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

CVE-2022-0214 affects custom popup builder. Severity is high (CVSS 7.5). The Custom Popup Builder WordPress plugin before 1.3.1 autoload data from its popup on every pages, as such data can be sent by unauthenticated user, and is not validated in length, this could cause a denial of service on the blog

Q: How urgent is CVE-2022-0214?

Priority 55/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.5REMOTEUPGRADE

CVE-2022-0214 is a high-severity flaw (CVSS 7.5) affecting custom popup builder. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Custom Popup Builder WordPress plugin before 1.3.1 autoload data from its popup on every pages, as such data can be sent by unauthenticated user, and is not validated in length, this could cause a denial of service on the blog

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.6% (top 24%)
CISA exploited list	No
Weakness	CWE-1284
Published	2022-02-14
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: custom popup builder project

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

Am I affected?

Timeline

2022-02-14 12:15 UTCPublished CVE record published
2026-06-17 04:20 UTCUpdated Record last modified

custom popup builder project custom popup builder UPGRADE

Affected: < 1.3.1

Fixed in: 1.3.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy custom-popup-builder || rpm -q custom-popup-builder || custom-popup-builder --version

2. UPGRADE to 1.3.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade custom-popup-builder

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade custom-popup-builder

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

custom popup builder: upgrade to 1.3.1. Exact commands for each OS are on this page.

Is CVE-2022-0214 being exploited?

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

CVE-2022-0214 affects custom popup builder. Severity is high (CVSS 7.5). The Custom Popup Builder WordPress plugin before 1.3.1 autoload data from its popup on every pages, as such data can be sent by unauthenticated user, and is not validated in length, this could cause a denial of service on the blog

How urgent is CVE-2022-0214?

Priority 55/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2022-28612 MEDIUM 5.4 UPGRADE Improper Access Control vulnerability leading to multiple Authenticated (contributor or higher user role) Stor

References

← Back to latest CVEs