Vulnerability Database · Packagist · Package report

buddypress/buddypress: vulnerability history, versions and safety

buddypress/buddypress is a package in the Packagist ecosystem. Vulert records 5 vulnerabilities for it across 120 releases, from Feb 2020 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded H3 M2
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
2 in the last 12 months

Most recent disclosure 10 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on buddypress/buddypress i

Updated on 23 Oct 2026

Careful: one of the 5 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 5 vulnerabilities on record across 6 years, 2 in the last year.

What to do: Plan around the 1 vulnerability with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 5 over 6 years · 2 in the last year i
  • Latest disclosure 10 Jun 2026 i
  • Highest CVSS 8.1 i
  • With no published fix 1 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 buddypress/buddypress, 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
14.4.0 H1 M1 No Details →
14.3.4 H1 M1 No Details →
14.3.3 H1 M1 No Details →
14.3.1 H1 M1 No Details →
14.2.1 H1 M1 No Details →
14.1.0 H1 M1 No Details →
14.0.0 H1 M1 No Details →
14.0.0-RC1 H1 M1 No Details →
14.0.0-beta2 H1 M1 No Details →
14.0.0-beta1 H1 M1 No Details →
12.7.0 H1 M1 No Details →
12.6.0 H1 M1 No Details →
12.5.3 H1 M1 No Details →
12.5.2 H1 M1 No Details →
12.5.1 H1 M1 No Details →
12.5.0 H1 M1 No Details →
12.4.1 H1 M1 No Details →
12.4.0 H1 M1 No Details →
12.3.0 H1 M1 No Details →
12.2.0 H1 M1 No Details →
12.1.1 H1 M1 No Details →
12.0.0 H1 M1 No Details →
12.0.0-RC1 H1 M1 No Details →
12.0.0-beta4 H1 M1 No Details →
12.0.0-beta3 H1 M1 No Details →
12.0.0-beta2 H1 M1 No Details →
12.0.0-beta1 H1 M1 No Details →
11.6.0 H1 M1 No Details →
11.5.2 H1 M1 No Details →
11.5.1 H1 M1 No Details →
11.4.4 H1 M1 No Details →
11.4.3 H1 M1 No Details →
11.4.2 H1 M1 No Details →
11.4.1 H1 M1 No Details →
11.4.0 H1 M1 No Details →
11.4.0-beta1 H1 M1 No Details →
11.3.2 H1 M1 No Details →
11.3.1 H1 M1 No Details →
11.2.0 H1 M1 No Details →
11.1.0 H1 M1 No Details →
11.0.0 H1 M1 No Details →
11.0.0-RC1 H1 M1 No Details →
11.0.0-beta3 H1 M1 No Details →
11.0.0-beta2 H1 M1 No Details →
11.0.0-beta1 H1 M1 No Details →
10.6.4 H1 M1 No Details →
10.6.3 H1 M1 No Details →
10.6.2 H1 M1 No Details →
10.6.1 H1 M1 No Details →
10.6.0 H1 M1 No Details →
10.5.0 H1 M1 No Details →
10.4.0 H1 M1 No Details →
10.3.0 H1 M1 No Details →
10.2.0 H1 M1 No Details →
10.1.0 H1 M1 No Details →
10.0.0 H1 M1 No Details →
10.0.0-RC1 H1 M1 No Details →
10.0.0-beta2 H1 M1 No Details →
10.0.0-beta1 H1 M1 No Details →
9.2.4 H1 M1 No Details →
9.2.3 H1 M1 No Details →
9.2.2 H1 M1 No Details →
9.2.1 H1 M1 No Details →
9.2.0 H1 M1 No Details →
9.1.1 H1 M1 No Details →
9.0.0 H1 M1 No Details →
9.0.0-RC1 H1 M1 No Details →
8.0.4 H1 M1 No Details →
8.0.3 H1 M1 No Details →
8.0.2 H1 M1 No Details →
8.0.0 H1 M1 No Details →
8.0.0-RC1 H1 M1 No Details →
8.0.0-beta2 H1 M1 No Details →
8.0.0-beta1 H1 M1 No Details →
7.3.4 H1 M1 No Details →
7.3.3 H1 M1 No Details →
7.3.2 H1 M1 No Details →
7.3.0 H1 M1 No Details →
7.2.1 H1 M1 No Details →
7.2.0 H2 M1 No Details →
7.1.0 H2 M1 No Details →
7.0.0 H2 M1 No Details →
7.0.0-RC2 H2 M1 No Details →
7.0.0-RC1 H2 M1 No Details →
7.0.0-beta2 H2 M1 No Details →
7.0.0-beta1 H2 M1 No Details →
6.4.3 H2 M1 No Details →
6.4.2 H2 M1 No Details →
6.4.0 H2 M1 No Details →
6.3.0 H2 M1 No Details →
6.2.0 H2 M1 No Details →
6.2.0-beta1 H2 M1 No Details →
6.1.0 H2 M1 No Details →
6.0.0 H2 M1 No Details →
6.0.0-RC2 H2 M1 No Details →
6.0.0-RC1 H2 M1 No Details →
6.0.0-beta2 H2 M1 No Details →
6.0.0-beta1 H2 M1 No Details →
5.2.2 H2 M1 No Details →
5.2.1 H2 M1 No Details →
5.2.0 H2 M1 No Details →
5.1.2 H2 M1 No Details →
5.1.1 H3 M1 No Details →
5.1.0 H3 M1 No Details →
5.1.0-beta1 H3 M1 No Details →
5.0.0 H3 M1 No Details →
5.0.0-RC2 H2 M1 No Details →
5.0.0-RC1 H2 M1 No Details →
5.0.0-beta2 H2 M1 No Details →
5.0.0-beta1 H2 M1 No Details →
4.4.1 H2 M1 No Details →
4.4.0 H2 M1 No Details →
4.3.0 H2 M1 No Details →
4.2.0 H2 M1 No Details →
4.1.0 H2 M1 No Details →
4.0.0 H2 M1 No Details →
4.0.0-RC1 H2 M1 No Details →
4.0.0-beta1 H2 M1 No Details →
3.2.1 H2 M1 No Details →
3.2.0 H2 M1 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2021 1
  • 2022 1
  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 5 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 buddypress/buddypress

Is buddypress/buddypress safe to use?

Vulert records 5 vulnerabilities for buddypress/buddypress in Packagist: 0 critical, 3 high, 2 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does buddypress/buddypress have?

5 vulnerabilities are recorded for buddypress/buddypress in the Packagist ecosystem: 0 critical, 3 high, 2 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 buddypress/buddypress vulnerabilities disclosed?

2 vulnerabilities were recorded for buddypress/buddypress in the last 12 months, and the oldest entry in this database dates to 24 Feb 2020. 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 buddypress/buddypress 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 buddypress/buddypress for upcoming vulnerabilities?

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