LiveActive security incident?Get immediate response
CVE Record

CVE-2021-27911: XSS vulnerability on contacts view

Mautic versions before 3.3.4/4.0.0 are vulnerable to an inline JS XSS attack through the contact's first or last name and triggered when viewing a contact's details page then clicking on the action drop down and hovering over the Campaigns button. Contact first and last name can be populated from different sources such as UI, API, 3rd party syncing, forms, etc.

HighCVSS 8.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Mautic allowed a stored cross-site scripting issue in contact first or last names. A malicious contact record could affect a staff user when they viewed contact details and interacted with the actions menu. The risk is high because contacts can originate from forms, APIs, integrations, or manual entry.

Executive priority

Prioritize remediation for internet-facing or integration-heavy Mautic deployments. This is not listed as known exploited in the provided sources, but the business impact can be material because staff sessions and sensitive marketing data may be exposed.

Technical view

CVE-2021-27911 is a CWE-79 XSS in Mautic before 3.3.4/4.0.0. The source describes inline JavaScript execution via contact first or last name, triggered in the contact details page action dropdown when hovering over Campaigns. CVSS 3.1 is 8.3 with network attack vector, high complexity, required user interaction, and changed scope.

Likely exposure

Exposure is likely where Mautic versions older than 3.3.4 or 4.0.0 process contact data from untrusted or semi-trusted sources such as public forms, APIs, third-party syncing, or manual imports.

Exploitation context

The bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires a user to view the affected contact details page and interact with the relevant menu, but contact data may enter from multiple sources.

Researcher notes

The source bundle gives a precise UI trigger and data fields but limited patch detail beyond fixed version boundaries. Do not assume other Mautic fields or products are affected without vendor evidence.

Mitigation direction

  • Upgrade Mautic to 3.3.4, 4.0.0, or a later supported release.
  • Review the GitHub security advisory for vendor-specific remediation details.
  • Restrict untrusted contact creation or synchronization paths until patched.
  • Audit and clean suspicious contact first and last name values.
  • Limit Mautic administrative access to trusted users.

Validation and detection

  • Inventory all Mautic deployments and confirm exact installed versions.
  • Verify no deployment remains below 3.3.4 or the 4.0.0 fixed boundary.
  • Review enabled contact intake paths: UI, API, forms, and third-party syncs.
  • Inspect recent contact records for unexpected script-like content in names.
  • Confirm patched staging behavior using safe, non-weaponized test data.
Prepared
Confidence
high
Sources
3

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-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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
cve · low confidence lookup

CVE-2021-27911 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 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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
2Source 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
8.3CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H1.66Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MauticMauticunspecified, unspecifiedListed
Weakness

CWE details

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

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.