cve.bz

CVE-2020-11001 torchbox wagtail: Cross-site Scripting

6.8 mediumExploit referenceEPSS 1.3%Fix available

Medium (6.8) in torchbox wagtail. EPSS 1.3% estimated probability of exploitation activity in the next 30 days. Fixed in wagtail 2.7.2, 2.8.1.

On this page
In Wagtail before versions 2.8.1 and 2.7.2, a cross-site scripting (XSS) vulnerability exists on the page revision comparison view within the Wagtail admin interface. A user with a limited-permission editor account for the Wagtail admin could potentially craft a page revision history that, when viewed by a user with higher privileges, could perform actions with that user's credentials. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin. Patched versions have been released as Wagtail 2.7.2 (for the LTS 2.7 branch) and Wagtail 2.8.1 (for the current 2.8 branch).

Severity

CVSS 3.1

6.8 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:N
EPSS
1.3% (unchanged from 1.3% a week ago; 1.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 71st percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-79 Improper Neutralization of Input During Web Page Generation (Cross-site Scripting)
CWE-80 Improper Neutralization of Script-Related HTML Tags in a Web Page
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

  • wagtail (PyPI): fixed in 2.7.2, 2.8.1

Ask an AI about this CVE

Show the promptExplain CVE-2020-11001 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-11001?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-11001?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-2020-11001 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:wagtailfrom 1.9 through 2.7.1
torchbox:wagtail2.8

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-v2wc-pfq2-5cm6PyPIwagtail>=1.9.0 <2.7.22.7.2
GHSA-v2wc-pfq2-5cm6PyPIwagtail>=2.8.0 <2.8.12.8.1
PYSEC-2020-152PyPIwagtail>=1.9 <2.7.22.7.2

Attack patterns (CAPEC)

  • CAPEC-18 XSS Targeting Non-Script Elements Likelihood: High · Severity: Very High
  • CAPEC-32 XSS Through HTTP Query Strings Likelihood: High · Severity: High
  • CAPEC-86 XSS Through HTTP Headers Likelihood: High · Severity: Very High
  • CAPEC-193 PHP Remote File Inclusion Likelihood: High · Severity: High
  • CAPEC-63 Cross-Site Scripting (XSS) Likelihood: High · Severity: Very High
  • CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
  • CAPEC-209 XSS Using MIME Type Mismatch Severity: Medium
  • CAPEC-588 DOM-Based XSS Likelihood: High · Severity: Very High
  • CAPEC-591 Reflected XSS Likelihood: High · Severity: Very High
  • CAPEC-592 Stored XSS Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON