cve.bz

CVE-2023-45809 torchbox wagtail: Forced Browsing

2.7 lowEPSS 0.6%Fix available

Low (2.7) in torchbox wagtail. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in wagtail 4.1.9, 5.0.5, 5.1.3.

On this page
Wagtail is an open source content management system built on Django. A user with a limited-permission editor account for the Wagtail admin can make a direct URL request to the admin view that handles bulk actions on user accounts. While authentication rules prevent the user from making any changes, the error message discloses the display names of user accounts, and by modifying URL parameters, the user can retrieve the display name for any user. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin. Patched versions have been released as Wagtail 4.1.8 (LTS), 5.0.5 and 5.1.3. The fix is also included in Release Candidate 1 of the forthcoming Wagtail 5.2 release. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Severity

CVSS 3.1

2.7 low
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 47th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-532 Insertion of Sensitive Information into Log File
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-425 Direct Request (Forced Browsing)
OWASP Top 10
A01:2025 Broken Access Control, A09:2025 Logging & Alerting Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-45809 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-45809?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-45809?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-45809 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
torchbox:wagtailbefore 4.1.9
torchbox:wagtailfrom 4.2 before 5.0.5
torchbox:wagtailfrom 5.1 before 5.1.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-fc75-58r8-rm3hPyPIwagtail<4.1.94.1.9
GHSA-fc75-58r8-rm3hPyPIwagtail>=4.2.0 <5.0.55.0.5
GHSA-fc75-58r8-rm3hPyPIwagtail>=5.1.0 <5.1.35.1.3
PYSEC-2023-219PyPIwagtail<4.1.9
>=4.2 <5.0.5
>=5.1 <5.1.3
4.1.9, 5.0.5, 5.1.3

Attack patterns (CAPEC)

  • CAPEC-215 Fuzzing for application mapping Likelihood: High · Severity: Low
  • CAPEC-87 Forceful Browsing Likelihood: High · Severity: High
  • CAPEC-127 Directory Indexing Likelihood: High · Severity: Medium
  • CAPEC-143 Detect Unpublicized Web Pages Severity: Low
  • CAPEC-144 Detect Unpublicized Web Services Severity: Low
  • CAPEC-668 Key Negotiation of Bluetooth Attack (KNOB) Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).

References

Check your stackJSON