How severe is CVE-2023-45809?

CVE-2023-45809 has a CVSS 3.x base score of 2.7, rated low severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.

Is CVE-2023-45809 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (36th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2023-45809?

CVE-2023-45809 affects Torchbox Wagtail. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2023-45809?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2023-45809 published?

CVE-2023-45809 was published on 2023-10-19 and last updated on 2026-06-17.

CVE-2023-45809

CVE-2023-45809 is a low-severity vulnerability in Torchbox Wagtail with a CVSS 3.x base score of 2.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-532.

Key facts

Severity: Low (CVSS 3.x base score 2.7)
EPSS exploit prediction: 0% (36th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-532
Affected product: Torchbox Wagtail
Published: 2023-10-19
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2023-45809?: 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.
How severe is CVE-2023-45809?: CVE-2023-45809 has a CVSS 3.x base score of 2.7, rated low severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2023-45809 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (36th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2023-45809?: CVE-2023-45809 affects Torchbox Wagtail. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2023-45809?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2023-45809 published?: CVE-2023-45809 was published on 2023-10-19 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:torchbox:wagtail:*:*:*:*:*:*:*:*

More vulnerabilities in Torchbox Wagtail

CVE-2026-54263 — High (CVSS 7.3): Wagtail is an open source content management system built on Django. In versions prior to 7.0.8, 7.3.3 and 7.4.2,…
CVE-2026-54261 — Medium (CVSS 6.5): Wagtail is an open source content management system built on Django. In versions prior to 7.0.8, 7.3.3 and 7.4.2, due…
CVE-2026-44200 — Medium (CVSS 6.5): Wagtail is an open source content management system built on Django. Prior to 7.0.7, 7.3.2, and 7.4, a CMS user with…
CVE-2026-44199 — Medium (CVSS 6.5): Wagtail is an open source content management system built on Django. Prior to 7.0.7, 7.3.2, and 7.4, a CMS user with…
CVE-2026-44197 — Medium (CVSS 6.5): Wagtail is an open source content management system built on Django. Prior to 7.0.7, 7.3.2, and 7.4, a CMS user without…
CVE-2024-39317 — Medium (CVSS 6.5): Wagtail is an open source content management system built on Django. A bug in Wagtail's `parse_query_string` would…

All CVEs affecting Torchbox Wagtail →

Other CWE-532 (Insertion of Sensitive Information into Log File) vulnerabilities

CVE-2022-36407 — Critical (CVSS 9.9): Insertion of Sensitive Information into Log File vulnerability in Hitachi Virtual Storage Platform, Hitachi Virtual…
CVE-2023-40029 — Critical (CVSS 9.9): Argo CD is a declarative continuous deployment for Kubernetes. Argo CD Cluster secrets might be managed declaratively…
CVE-2021-32724 — Critical (CVSS 9.9): check-spelling is a github action which provides CI spell checking. In affected versions and for a repository with the…
CVE-2026-49200 — Critical (CVSS 9.8): The acer_cgi.log file in the device firmware is accessible without authentication via the web interface. This file…
CVE-2026-22778 — Critical (CVSS 9.8): vLLM is an inference and serving engine for large language models (LLMs). From 0.8.3 to before 0.14.1, when an invalid…
CVE-2025-11008 — Critical (CVSS 9.8): The CE21 Suite plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and…

Browse all CWE-532 (Insertion of Sensitive Information into Log File) vulnerabilities →