Skip to content

Volto affected by possible DoS by invoking specific URL by anonymous user

High severity GitHub Reviewed Published Aug 28, 2025 in plone/volto • Updated Aug 28, 2025

Package

npm @plone/volto (npm)

Affected versions

< 16.34.0
>= 17.0.0, < 17.22.1
>= 18.0.0, < 18.24.0
>= 19.0.0-alpha.1, < 19.0.0-alpha.4

Patched versions

16.34.0
17.22.1
18.24.0
19.0.0-alpha.4

Description

Impact

When visiting a specific URL, an anonymous user could cause the NodeJS server part of Volto to quit with an error.

Patches

The problem has been patched and the patch has been backported to Volto major versions down until 16. It is advised to upgrade to the latest patch release of your respective current major version:

Workarounds

Make sure your setup automatically restarts processes that quit with an error. This won't prevent a crash, but it minimises downtime.

Report

The problem was discovered by FHNW, a client of Plone provider kitconcept, who shared it with the Plone Zope Security Team (security@plone.org).

References

@mauritsvanrees mauritsvanrees published to plone/volto Aug 28, 2025
Published to the GitHub Advisory Database Aug 28, 2025
Reviewed Aug 28, 2025
Published by the National Vulnerability Database Aug 28, 2025
Last updated Aug 28, 2025

Severity

High

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
None
Integrity
None
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:N/I:N/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.
(16th percentile)

Weaknesses

Improper Handling of Exceptional Conditions

The product does not handle or incorrectly handles an exceptional condition. Learn more on MITRE.

CVE ID

CVE-2025-58047

GHSA ID

GHSA-xjhf-7833-3pm5

Source code

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