Vulnerability Database · Packagist · Package report

wpglobus/wpglobus: vulnerability history, versions and safety

wpglobus/wpglobus is a package in the Packagist ecosystem. Vulert records 7 vulnerabilities for it across 79 releases, first recorded in May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded H1 M6
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.

Vulert verdict on wpglobus/wpglobus i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 7 vulnerabilities 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 7 over 1 year · 0 in the last year i
  • Latest disclosure 14 May 2022 i
  • Highest CVSS 8.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 wpglobus/wpglobus, 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
1.9.6 H1 M6 Yes Details →
1.9.5 H1 M6 Yes Details →
1.9.4 H1 M6 Yes Details →
1.9.3 H1 M6 Yes Details →
1.9.2 H1 M6 Yes Details →
1.9.1 H1 M6 Yes Details →
1.9.0 H1 M6 Yes Details →
1.8.9 H1 M6 Yes Details →
1.8.8 H1 M6 Yes Details →
1.8.7 H1 M6 Yes Details →
1.8.6 H1 M6 Yes Details →
1.8.5 H1 M6 Yes Details →
1.8.4 H1 M6 Yes Details →
1.8.3 H1 M6 Yes Details →
1.8.2 H1 M6 Yes Details →
1.8.1 H1 M6 Yes Details →
1.8.0 H1 M6 Yes Details →
1.7.12 H1 M6 Yes Details →
1.7.11 H1 M6 Yes Details →
1.7.10 H1 M6 Yes Details →
1.7.9 H1 M6 Yes Details →
1.7.8.2 H1 M6 Yes Details →
1.7.8.1 H1 M6 Yes Details →
1.7.8 H1 M6 Yes Details →
1.7.7.2 H1 M6 Yes Details →
1.7.7.1 H1 M6 Yes Details →
1.7.7 H1 M6 Yes Details →
1.7.6 H1 M6 Yes Details →
1.7.5 H1 M6 Yes Details →
1.7.4 H1 M6 Yes Details →
1.7.3 H1 M6 Yes Details →
1.7.2 H1 M6 Yes Details →
1.7.1 H1 M6 Yes Details →
1.7.0 H1 M6 Yes Details →
1.6.9 H1 M6 Yes Details →
1.6.8 H1 M6 Yes Details →
1.6.7 H1 M6 Yes Details →
1.6.6 H1 M6 Yes Details →
1.6.5 H1 M6 Yes Details →
1.6.4 H1 M6 Yes Details →
1.6.3 H1 M6 Yes Details →
1.6.2 H1 M6 Yes Details →
1.6.1 H1 M6 Yes Details →
1.6.0 H1 M6 Yes Details →
1.5.10 H1 M6 Yes Details →
1.5.9 H1 M6 Yes Details →
1.5.8 H1 M6 Yes Details →
1.5.7 H1 M6 Yes Details →
1.5.6 H1 M6 Yes Details →
1.5.5 H1 M6 Yes Details →
1.5.4.1 H1 M6 Yes Details →
1.5.4 H1 M6 Yes Details →
1.5.3 H1 M6 Yes Details →
1.5.2 H1 M6 Yes Details →
1.5.1 H1 M6 Yes Details →
1.5.0 H1 M6 Yes Details →
1.4.9 H1 M6 Yes Details →
1.4.8 H1 M6 Yes Details →
1.4.7 H1 M6 Yes Details →
1.4.6 H1 M6 Yes Details →
1.4.5 H1 M6 Yes Details →
1.4.4 H1 M6 Yes Details →
1.4.3 H1 M6 Yes Details →
1.4.2 H1 M6 Yes Details →
1.4.1 H1 M6 Yes Details →
1.4.0 H1 M6 Yes Details →
1.3.2 H1 M6 Yes Details →
1.3.1 H1 M6 Yes Details →
1.3.0 H1 M6 Yes Details →
1.2.9 H1 M6 Yes Details →
1.2.8 H1 M6 Yes Details →
1.2.7 H1 M6 Yes Details →
1.2.6 H1 M6 Yes Details →
1.2.5 H1 M6 Yes Details →
1.2.4 H1 M6 Yes Details →
1.2.3 H1 M6 Yes Details →
1.2.2 H1 M6 Yes Details →
1.2.1 H1 M6 Yes Details →
1.2.0 H1 M6 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 7

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

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 wpglobus/wpglobus

Is wpglobus/wpglobus safe to use?

Vulert records 7 vulnerabilities for wpglobus/wpglobus in Packagist: 0 critical, 1 high, 6 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 wpglobus/wpglobus have?

7 vulnerabilities are recorded for wpglobus/wpglobus in the Packagist ecosystem: 0 critical, 1 high, 6 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 wpglobus/wpglobus vulnerabilities disclosed?

0 vulnerabilities were recorded for wpglobus/wpglobus in the last 12 months, and the oldest entry in this database dates to 13 May 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 wpglobus/wpglobus 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 wpglobus/wpglobus for upcoming vulnerabilities?

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