LiveActive security incident?Get immediate response
CVE Record

CVE-2021-37627: Privilege escalation via form generator

Contao is an open source CMS that allows creation of websites and scalable web applications. In affected versions it is possible to gain privileged rights in the Contao back end. Installations are only affected if they have untrusted back end users who have access to the form generator. All users are advised to update to Contao 4.4.56, 4.9.18 or 4.11.7. As a workaround users may disable the form generator or disable the login for untrusted back end users.

HighCVSS 8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Contao CMS installations with untrusted backend users who can use the form generator may let those users gain privileged backend rights. This matters because compromise starts from an existing backend account but can expand to control over site data, configuration, and availability.

Executive priority

Treat as high priority for Contao sites with multiple backend users, contractors, customers, or shared editorial access. Single-admin sites have lower practical exposure but should still patch during the next maintenance window.

Technical view

CVE-2021-37627 is a CWE-269 privilege management flaw in Contao. Affected ranges are <4.4.56, 4.5.0 to <4.9.18, and 4.10.0 to <4.11.7. CVSS 3.1 is 8.0 with high complexity, high privileges required, changed scope, and high CIA impact.

Likely exposure

Exposure is limited to Contao deployments in affected versions where untrusted backend users have access to the form generator. Public visitors without backend access are not identified as the affected threat model in the provided sources.

Exploitation context

The bundle does not cite active exploitation, KEV listing, or public exploit details. Abuse requires existing backend access according to the advisory condition, with CVSS marking privileges required as high.

Researcher notes

The key condition is not broad internet reachability alone; it is affected Contao versions plus untrusted backend users with form generator access. Sources do not describe exploit mechanics, so validation should focus on version, role, and feature exposure.

Mitigation direction

  • Update Contao to 4.4.56, 4.9.18, 4.11.7, or later supported releases.
  • Temporarily disable the form generator if immediate upgrade is not possible.
  • Disable login for untrusted backend users until patched.
  • Review Contao vendor guidance before production rollout.

Validation and detection

  • Inventory Contao versions across production, staging, and managed customer sites.
  • Check whether untrusted backend users can access the form generator.
  • Confirm upgraded systems report Contao 4.4.56, 4.9.18, 4.11.7, or later.
  • Review backend user roles for unnecessary form generator permissions.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-269: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-37627 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H1.36Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8High
CVSS 3.1 vector shape for CVE-2021-37627Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
contaocontao< 4.4.56, >= 4.5.0, < 4.9.18, >= 4.10.0, < 4.11.7Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-269 · source CWE mapping

Improper Privilege Management

Improper Privilege Management represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.