CVE-2021-37626: PHP file inclusion via insert tags
Noroxi assessment
Priority: Monitor (action score 28/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: 1.2% (FIRST EPSS); higher than 69.6% of all records.
- Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: contao/contao (Packagist) 4.4.56, 4.11.7, 4.9.18; contao/core-bundle (Packagist) 4.4.56, 4.11.7, 4.9.18.
Low priority for now. Upgrade to contao/contao (Packagist) 4.4.56, 4.11.7, 4.9.18; contao/core-bundle (Packagist) 4.4.56, 4.11.7, 4.9.18 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 is an open source CMS that allows you to create websites and scalable web applications. In affected versions it is possible to load PHP files by entering insert tags in the Contao back end. Installations are only affected if they have untrusted back end users who have the rights to modify fields that are shown in the front end. Update to Contao 4.4.56, 4.9.18 or 4.11.7 to resolve. If you cannot update then disable the login for untrusted back end users.
- Published
- Aug 11, 2021
- Updated
- Jun 17, 2026
- EPSS
- 1.2% · 69th percentile
- CWE
- CWE-94
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.2%
CNA vs NVD score
- NVD
- 7.2
- CNA · GitHub_M
- 7.2
- agree
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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.
| Vendor | Product | CPE |
|---|---|---|
| contao | contao | cpe:2.3:a:contao:contao |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- contao contao4.4.0 and later · before 4.4.56
- contao contao4.9.0 and later · before 4.9.18
- contao contao4.11.0 and later · before 4.11.7
- contao contao4.0.0
- contao contao4.1.0
- contao contao4.10.0
- contao contao4.2.0
- contao contao4.3.0
- contao contao4.5.0
- contao contao4.6.0
- contao contao4.7.0
- contao contao4.8.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
contao contao
- >= 4.0.0, < 4.4.56, >= 4.5.0, < 4.9.18, >= 4.10.0, < 4.11.7affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Packagist | contao/contao | from 4.0.0 · before 4.4.56 | 4.4.56 |
| Packagist | contao/contao | from 4.10.0 · before 4.11.7 | 4.11.7 |
| Packagist | contao/contao | from 4.5.0 · before 4.9.18 | 4.9.18 |
| Packagist | contao/core-bundle | from 4.0.0 · before 4.4.56 | 4.4.56 |
| Packagist | contao/core-bundle | from 4.10.0 · before 4.11.7 | 4.11.7 |
| Packagist | contao/core-bundle | from 4.5.0 · before 4.9.18 | 4.9.18 |
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-2020-25768Oct 7, 2020 · Contao before 4.4.52, 4.9.x before 4.9.6, and 4.10.x before 4.10.1 have Improper Input Validation.21Monitor
- ← EarlierCVE-2021-35210Jun 23, 2021 · Contao 4.5.x through 4.9.x before 4.9.16, and 4.10.x through 4.11.x before 4.11.5, allows XSS.24Monitor
- Later →CVE-2021-37627Aug 11, 2021 · Privilege escalation via form generator28Monitor
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 |
|---|---|---|
| Packagist:contao/contao | 4.11.7 | Package registry (OSV) |
| Packagist:contao/contao | 4.4.56 | Package registry (OSV) |
| Packagist:contao/contao | 4.9.18 | Package registry (OSV) |
| Packagist:contao/core-bundle | 4.11.7 | Package registry (OSV) |
| Packagist:contao/core-bundle | 4.4.56 | Package registry (OSV) |
| Packagist:contao/core-bundle | 4.9.18 | Package registry (OSV) |
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.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-94 · Improper Control of Generation of Code ('Code Injection')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
nvd-primary
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)
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.