PXLSecurity LTD., Sofia, Bulgaria Offensive security since 2014[email protected]

CVE-2025-50674

OpenMediaVault local privilege escalation

A flaw in the changePassword method lets a local authenticated attacker escalate privileges to root.

Local privilege escalationOpenMediaVaultHigh

Technical summary

OpenMediaVault is a Debian-based network-attached storage distribution. Its PHP system layer exposes a changePassword method in /usr/share/php/openmediavault/system/user.inc that is reachable by an authenticated local user.

The method does not validate its input strictly enough before that input reaches a privileged operation. The published record classifies the root cause as improper input validation (CWE-20) combined with improper privilege management (CWE-269); the researcher’s write-up describes the fix as adding input validation to prevent newline injection.

Impact

A local authenticated account becomes root on the appliance. On a NAS that means full control of the host and of every share and dataset it serves.

An issue was discovered in the changePassword method in file /usr/share/php/openmediavault/system/user.inc in OpenMediaVault 7.4.17 allowing local authenticated attackers to escalate privileges to root.

Remediation

The OpenMediaVault project addressed the issue in later versions. The published record does not name a fixed version number, so none is stated here.

Published severity

Published byVersionBase scoreVector
CISA-ADPCVSS 3.1 7.8 High CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Disclosure timeline

  1. 2025-08-22CVE record published
  2. 2025-08-24Researcher’s technical write-up published

Only publicly documented dates are shown. Where a step in the process was not published, it is not listed.

References

Credit

Researcher: Ivan Spiridonov

The CVE record carries no formal credits field. Both of its references are Ivan Spiridonov’s own published write-up and proof-of-concept, which is the basis for the credit shown here.

This is the work we do commercially

Vulnerability research and penetration testing by the same engineers who found this issue. Every report carries reproduction steps, impact and a retest.

We publish advisories, not exploits. Each entry describes the vulnerability class and impact at the level the vendor advisory does, and links to the authoritative records. Where public proof-of-concept code exists we link to it rather than reproduce it.

How we disclose

Every issue here was reported to the vendor or to a coordinating programme before publication. We publish only once a fix is available or the coordinated disclosure window has elapsed.

Want this kind of scrutiny on your own software?

Tell us what you want to protect. A senior tester will help you agree the scope and next steps. We usually reply within one business day.

Confidential from the first conversation

We can sign your NDA before you share sensitive details. Your enquiry is covered by our privacy policy.

How we protect your information · Privacy policy