CVE-2026-126663: Contao 4.0.0 before 5.3.54, 5.4.0 before 5.7.17, and 6.0.0 before 6.0.6 Path Traversal via Image Insert Tag
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.36% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Contao Contao 5.3.54, 5.7.17, 6.0.6.
Low priority for now. Upgrade to Contao Contao 5.3.54, 5.7.17, 6.0.6 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Contao 4.0.0 before 5.3.54, 5.4.0 before 5.7.17, and 6.0.0 before 6.0.6 contains a path traversal vulnerability that allows content editors to read image files anywhere on the filesystem via the {{image::}} insert tag. Attackers can embed percent-encoded sequences like ..%2f that pass Validator::isInsecurePath() before rawurldecode(), making the frontend resize and serve readable image files outside the files directory.
- Published
- Nov 11, 2026
- Updated
- Nov 11, 2026
- EPSS
- 0.3% · 30th percentile
- CWE
- CWE-180
Report tools
Action score
21
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CNA vs NVD score
- NVD
- —
- CNA · VulnCheck
- 5.3
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.
Contao Contao
- 4.0.0 and later · before 5.3.54affected · semver
- 5.4.0-RC1 and later · before 5.7.17affected · semver
- 6.0.0-RC1 and later · before 6.0.6affected · semver
Same product
contao: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-26265Contao Managed Edition v1.5.0 was discovered to contain a remote command execution (RCE) vulnerability via the component php_cli parameter.48Plan
- CVE-2019-11512Contao 4.x allows SQL Injection.39Monitor
- CVE-2026-107845Contao: Cross-site scripting in the comments bundle37Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-107850Oct 9, 2026 · Contao: Improper access control in the preview links module17Monitor
- ← EarlierCVE-2026-107851Oct 9, 2026 · Contao: Improper access control in the table access voter17Monitor
- ← EarlierCVE-2026-126662Nov 11, 2026 · Contao 4.0.0 before 5.3.54, 5.4.0 before 5.7.17, and 6.0.0 before 6.0.6 Filemount Bypass via Edit-Multiple28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Contao Contao | 5.3.54 | Vendor (CNA) |
| Contao Contao | 5.7.17 | Vendor (CNA) |
| Contao Contao | 6.0.6 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 13, 2026+2 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- AlpetGexhafinder
- ausiremediation developer
Not on record for this CVE: variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-180 · Incorrect Behavior Order: Validate Before CanonicalizeCVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Leverage Alternate EncodingCAPEC-267likelihood: High · High
- Using Leading 'Ghost' Character Sequences to Bypass Input FiltersCAPEC-3likelihood: Medium · Medium
- Using Unicode Encoding to Bypass Validation LogicCAPEC-71likelihood: Medium · High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
- Using UTF-8 Encoding to Bypass Validation LogicCAPEC-80likelihood: High · High
ATT&CK techniques
Change log (2)
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- github.com/contao/contao/commit/0f7989eb5b28d85dcd441ef22f80f8af4f56433e
- github.com/contao/contao/commit/688c0f6213afbd000cd22ad0a44555eca80b40ab
- github.com/contao/contao/commit/e820e3c9d79a5c07f274558513c8db08a79bf804
- github.com/contao/contao/releases/tag/5.3.54
- github.com/contao/contao/releases/tag/5.7.17
- github.com/contao/contao/releases/tag/6.0.6
- github.com/contao/contao/security/advisories/GHSA-r7cf-mfp4-r23h
- www.vulncheck.com/advisories/contao-4.0.0-before-5.3.54-5.4.0-before-5.7.17-and-6.0.0-before-6.0.6-path-traversal-via-image-insert-tag
Vendor advisories and official records. Exploit/PoC links are deliberately left out.