Miggo Logo

CVE-2021-27911: XSS vulnerability on contacts view

8.4

CVSS Score
3.1

Basic Information

EPSS Score
0.56975%
Published
9/1/2021
Updated
2/7/2024
KEV Status
No
Technology
TechnologyPHP

Technical Details

CVSS Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Package NameEcosystemVulnerable VersionsFirst Patched Version
mautic/corecomposer< 3.3.43.3.4
mautic/corecomposer>= 4.0.0-alpha1, < 4.0.04.0.0

Vulnerability Intelligence
Miggo AIMiggo AI

Miggo AIRoot Cause Analysis

The vulnerability stems from unescaped contact names being rendered in JavaScript contexts. Key indicators:

  1. The attack triggers via hover interaction with campaign buttons, suggesting inline JS event handlers
  2. First/last names are user-controlled inputs from multiple sources
  3. XSS occurs despite standard HTML escaping because the payload exists in JS context
  4. The patch versions (3.3.4/4.0.0) likely added JS-specific escaping in template rendering

While exact code isn't available, Mautic's architecture suggests:

  • DynamicContentExtension handles content rendering
  • LeadController's view action prepares contact data These components would be responsible for properly escaping outputs in different contexts. The high confidence for DynamicContentExtension comes from its direct role in content rendering, while the controller gets medium confidence as the data source.

Vulnerable functions

Only Mi**o us*rs **n s** t*is s**tion

WAF Protection Rules

WAF Rule

### Imp**t M*uti* v*rsions ***or* *.*.*/*.*.* *r* vuln*r**l* to *n inlin* JS XSS *tt**k t*rou** t** *ont**t's *irst or l*st n*m* *n* tri***r** w**n vi*win* * *ont**t's **t*ils p*** t**n *li*kin* on t** **tion *rop *own *n* *ov*rin* ov*r t** **mp*i*ns

Reasoning

T** vuln*r**ility st*ms *rom un*s**p** *ont**t n*m*s **in* r*n**r** in J*v*S*ript *ont*xts. K*y in*i**tors: *. T** *tt**k tri***rs vi* *ov*r int*r**tion wit* **mp*i*n *uttons, su***stin* inlin* JS *v*nt **n*l*rs *. *irst/l*st n*m*s *r* us*r-*ontroll*