VulertSecurity VulertSecurity

Vulnerability Database · Packagist · Package report

phpems/phpems: vulnerability history, versions and safety

phpems/phpems is a package in the Packagist ecosystem. Vulert records 1 vulnerability for it across 16 releases, first recorded in Dec 2023. 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 M1
i
1 with no fix published

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

See the unfixed vulnerabilities →
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 phpems/phpems vulnerabilities

Vulert verdict on phpems/phpems i

Updated on 23 Oct 2026

Careful: one of the 1 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 1 vulnerability on record across 1 year, none 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 1 over 1 year · 0 in the last year i
  • Latest disclosure 10 Dec 2023 i
  • Highest CVSS 6.3 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 phpems/phpems, 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
v6.1.3 M1 No Details →
v6.1.2 M1 No Details →
v6.1.1 M1 No Details →
v6.1.0 M1 No Details →
v6.0.10 M1 No Details →
v6.0.9 M1 No Details →
v6.0.8 M1 No Details →
v6.0.7 M1 No Details →
v6.0.6 M1 No Details →
v6.0.5 M1 No Details →
v6.0.4 M1 No Details →
v6.0.3 M1 No Details →
v6.0.2.1 M1 No Details →
v6.0.2 M1 No Details →
v6.0.1 M1 No Details →
v6.0.0 M1 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 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 phpems/phpems

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-6654: PHPEMS Deserialization of Untrusted Data vulnerability 6.3 medium No fix published 10 Dec 2023

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

Is phpems/phpems safe to use?

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

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

0 vulnerabilities were recorded for phpems/phpems in the last 12 months, and the oldest entry in this database dates to 10 Dec 2023. 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 phpems/phpems 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 phpems/phpems for upcoming vulnerabilities?

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