Skip to main content
Mallory
MediumVulnerability

CVE-2011-4335: XSS in Contao <2.10.2 index.php PATH_INFO

Published Nov 28, 2011 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS4.3Medium · v2
EPSS1.5%75th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Contao
IdentifiersCVE-2011-4335CWE-79 · Improper Neutralization of Input…

Multiple cross-site scripting (XSS) vulnerabilities exist in Contao before version 2.10.2. The vulnerabilities allow remote attackers to inject arbitrary web script or HTML via the PATH_INFO parameter to index.php in the context of (1) teachers.html or (2) teachers/ actions. This occurs due to insufficient sanitization of user-supplied input in the PATH_INFO variable, which is reflected in the application's output.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote attackers to execute arbitrary JavaScript in the context of the victim's browser session, potentially leading to session hijacking, credential theft, or other attacks leveraging the user's authenticated session.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, implement input validation and output encoding for the PATH_INFO parameter in index.php. Additionally, consider deploying a web application firewall (WAF) to filter malicious input targeting XSS vectors.

Remediation

Patch, then assume compromise.

Upgrade Contao to version 2.10.2 or later, where the input validation and output encoding issues in the affected PATH_INFO handling have been addressed.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
ContaoContao Cmsapplication
FAQ

Frequently asked questions

Is CVE-2011-4335 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2011-4335 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2011-4335?
As of Oct 16, 2026, Mallory has not confirmed a public exploit for CVE-2011-4335. 1 candidate exploit record is not yet analyzed.
Is there a patch for CVE-2011-4335?
Upgrade Contao to version 2.10.2 or later, where the input validation and output encoding issues in the affected PATH_INFO handling have been addressed.
What products are affected by CVE-2011-4335?
Contao Cms.
How severe is CVE-2011-4335?
CVE-2011-4335 has a CVSS v2 score of 4.3 (Medium) and an EPSS score of 1.5% (75th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.