Skip to content

phpVMS has an /importer authorization bypass causing full database wipe

Critical severity GitHub Reviewed Published Apr 23, 2026 in phpvms/phpvms • Updated May 13, 2026

Package

composer nabeel/phpvms (Composer)

Affected versions

< 7.0.6

Patched versions

7.0.6

Description

Security Advisory: Unauthenticated Access to Legacy Import Feature

Severity: Critical
Affected versions: phpVMS 7.x (up to 7.0.5)
Fixed in: v7.0.6
Component: Legacy importer

Summary

A critical vulnerability in phpVMS 7.x allowed unauthenticated access to a legacy import feature. Although this feature is deprecated, parts of it remained accessible and operational.

Impact

A remote attacker could trigger internal processes that modify or delete application data, potentially resulting in:

  • Data loss
  • Service disruption

No authentication was required.

Remediation

  • Update immediately to the latest patched version
  • If unable to update:
    • The release link has instructions on how to fix it (it's a one-line fix to comment out the routes)

Affected Versions

  • Affected: phpVMS 7.x ≤ 7.0.5
  • Not affected: phpVMS >= 7.0.6, v8 (feature removed from public access)

References

@nabeelio nabeelio published to phpvms/phpvms Apr 23, 2026
Published to the GitHub Advisory Database May 4, 2026
Reviewed May 4, 2026
Published by the National Vulnerability Database May 9, 2026
Last updated May 13, 2026

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(85th percentile)

Weaknesses

Improper Access Control

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Learn more on MITRE.

Missing Authentication for Critical Function

The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. Learn more on MITRE.

Missing Authorization

The product does not perform an authorization check when an actor attempts to access a resource or perform an action. Learn more on MITRE.

CVE ID

CVE-2026-42569

GHSA ID

GHSA-fv26-4939-62fh

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.
⚡