Skip to content

Ghost vulnerable to information disclosure of private API fields

High severity GitHub Reviewed Published May 3, 2023 in TryGhost/Ghost • Updated Nov 7, 2023

Package

npm ghost (npm)

Affected versions

< 5.46.1

Patched versions

5.46.1

Description

Impact

Due to a lack of validation when filtering on the public API endpoints, it is possible to reveal private fields via a brute force attack.

Ghost(Pro) has already been patched. We can find no evidence that the issue was exploited on Ghost(Pro) prior to the patch being added.

Self-hosters are impacted if running Ghost a version below v5.46.1. Immediate action should be taken to secure your site - see patches and workarounds below.

Patches

v5.46.1 contains a fix for this issue.

Workarounds

Add a block for requests to /ghost/api/content/* where the filter query parameter contains password or email.

For more information

If you have any questions or comments about this advisory:

References

@daniellockyer daniellockyer published to TryGhost/Ghost May 3, 2023
Published to the GitHub Advisory Database May 3, 2023
Reviewed May 3, 2023
Published by the National Vulnerability Database May 8, 2023
Last updated Nov 7, 2023

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
High
Integrity
None
Availability
None

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:H/I:N/A:N

EPSS score

0.159%
(53rd percentile)

Weaknesses

CVE ID

CVE-2023-31133

GHSA ID

GHSA-r97q-ghch-82j9

Source code

Credits

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