CVE-2021-39351: The WP Bannerize WordPress plugin is vulnerable to authenticated SQL injection via the id parameter found in t

Routine

MEDIUM 6.5UPGRADE

CVE-2021-39351 is a medium-severity flaw (CVSS 6.5) affecting wp bannerize. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The WP Bannerize WordPress plugin is vulnerable to authenticated SQL injection via the id parameter found in the ~/Classes/wpBannerizeAdmin.php file which allows attackers to exfiltrate sensitive information from vulnerable sites. This issue affects versions 2.0.0 - 4.0.2.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	1.1% (top 34%)
CISA exploited list	No
Weakness	CWE-89
Published	2021-10-06
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: wp bannerize project

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

Am I affected?

Timeline

2021-10-06 16:15 UTCPublished CVE record published
2026-06-17 04:03 UTCUpdated Record last modified

wp bannerize project wp bannerize UPGRADE

Affected: >= 2.0.0 and <= 4.0.2

Fixed in: newer than 4.0.2

Safe to downgrade to: a release before 2.0.0

1. Check installed version

apt-cache policy wp-bannerize || rpm -q wp-bannerize || wp-bannerize --version

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

sudo apt update && sudo apt install --only-upgrade wp-bannerize

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wp-bannerize

Note

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

3. If no update is available yet, DOWNGRADE to a release before 2.0.0 (Debian / Ubuntu)

apt-cache madison wp-bannerize sudo apt install wp-bannerize=<VERSION_BEFORE_2.0.0> sudo apt-mark hold wp-bannerize

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list wp-bannerize sudo dnf downgrade wp-bannerize-<VERSION_BEFORE_2.0.0> sudo dnf versionlock add wp-bannerize

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

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-2021-39351?

wp bannerize: upgrade to newer than 4.0.2. Exact commands for each OS are on this page.

Is CVE-2021-39351 being exploited?

CVE-2021-39351 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-2021-39351 affect?

CVE-2021-39351 affects wp bannerize. Severity is medium (CVSS 6.5). The WP Bannerize WordPress plugin is vulnerable to authenticated SQL injection via the id parameter found in the ~/Classes/wpBannerizeAdmin.php file which allows attackers to exfiltrate sensitive information from vulnerable sites. This issu

How urgent is CVE-2021-39351?

Priority 39/100. No elevated risk signals yet.

Software pages

WordPress vulnerabilities · PHP vulnerabilities

References

← Back to latest CVEs