VulertSecurity VulertSecurity

Vulnerability Database · Packagist · Package report

bmarshall511/wordpress_zero_spam: vulnerability history, versions and safety

bmarshall511/wordpress_zero_spam is a package in the Packagist ecosystem. Vulert records 1 vulnerability for it across 17 releases, first recorded in Mar 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded C1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all bmarshall511/wordpress_zero_spam vulnerabilities

Vulert verdict on bmarshall511/wordpress_zero_spam i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 15 Mar 2022. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 1 vulnerability on record across 1 year, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 15 Mar 2022 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for bmarshall511/wordpress_zero_spam, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
4.10.2 C1 Yes Details →
v5.2.8 C1 Yes Details →
v5.2.7 C1 Yes Details →
v5.2.5 C1 Yes Details →
v5.2.4 C1 Yes Details →
v5.2.2 C1 Yes Details →
v5.2.0 C1 Yes Details →
v5.1.6 C1 Yes Details →
v5.1.5 C1 Yes Details →
v5.1.4 C1 Yes Details →
v5.1.3 C1 Yes Details →
v5.1.2 C1 Yes Details →
v5.1.1 C1 Yes Details →
v5.1.0 C1 Yes Details →
v5.0.13 C1 Yes Details →
v5.0.12 C1 Yes Details →
v5.0.8 C1 Yes Details →

Newest 17 of 17 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for bmarshall511/wordpress_zero_spam

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-0254: SQL Injection in WordPress Zero Spam WordPress plugin 9.8 critical 5.2.13 15 Mar 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About bmarshall511/wordpress_zero_spam

Is bmarshall511/wordpress_zero_spam safe to use?

Vulert records 1 vulnerabilities for bmarshall511/wordpress_zero_spam in Packagist: 1 critical, 0 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does bmarshall511/wordpress_zero_spam have?

1 vulnerability is recorded for bmarshall511/wordpress_zero_spam in the Packagist ecosystem: 1 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new bmarshall511/wordpress_zero_spam vulnerabilities disclosed?

0 vulnerabilities were recorded for bmarshall511/wordpress_zero_spam in the last 12 months, and the oldest entry in this database dates to 15 Mar 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of bmarshall511/wordpress_zero_spam are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor bmarshall511/wordpress_zero_spam for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the bmarshall511/wordpress_zero_spam version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.