CVE-2026-133876 json
flask-calendar before commit bfde72e Stored XSS via Task Details
published yesterday modified yesterday also EUVD-2026-131650
- cvss
- 5.1
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 32%
- public exploits
- 0
- none known
Summary
Kartones flask-calendar before commit bfde72e contains a stored cross-site scripting vulnerability because task_details_for_markup returns unescaped content rendered with the |safe filter. Authenticated shared calendar members can store script in task details that executes for other members, letting attackers read and modify their private calendars.
Patch / fix
Is CVE-2026-133876 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-21).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 5.1 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N |
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
Affected products
- Kartones flask-calendar
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/Kartones/flask-calendar/commit/bfde72eb3822a2584ae5afebae174a3c1c8593f9
patch
-
github.com
/Kartones/flask-calendar/issues/223
issue-tracking
-
github.com
/Kartones/flask-calendar
product
-
github.com
/Kartones/flask-calendar/blob/4cc5f6162c587524ce3dcaa3fe46ec244aa47afa/flask_calendar/templates/calendar.html#
technical-description
-
vulncheck.com
/advisories/flask-calendar-before-commit-bfde72e-stored-xss-via-task-details
third-party-advisory
Sources
- CVE List CVE-2026-133876
- NVD CVE-2026-133876
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.