How severe is CVE-2011-2935?

CVE-2011-2935 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2011-2935?

CVE-2011-2935 affects the following packages: elgg/elgg (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2011-2935?

Update elgg/elgg to 1.7.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-2935 is resolved across your whole dependency graph.

How do I detect CVE-2011-2935 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for elgg/elgg, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2011-2935 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2011-2935 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2011-2935, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2011-2935?

CVE-2011-2935 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 65th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2011-2935?

CVE-2011-2935 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2011-2935 published, and has it been updated?

CVE-2011-2935 was published on April 22, 2022 and was last updated on January 12, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

CVE-2011-2935 — elgg

MEDIUMFix: Elgg/Elgg@2843b4f

CVE-2011-2935 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in elgg/elgg. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for elgg/elgg — see the affected versions and patch details below.

Elgg Reflected XSS Vulnerability

Published

Apr 22, 2022

Updated

Jan 12, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐘elgg/elgg

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

VULNERABILITY DESCRIPTION

The internalname parameter is not properly sanitized, which allows attacker to conduct Cross Site Scripting attack. This may allow an attacker to create a specially crafted URL that would execute arbitrary script code in a victim's browser

PROOF-OF-CONCEPT/EXPLOIT

http://localhost/pg/embed/media?internalname=%20%22onmouseover=%22alert%28/XSS/%29%22style=%22width:3000px!important;height:3000px!important;z-index:999999;position:absolute!important;left:0;top:0;%22%20x=%22

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`elgg/elgg`	all versions	1.7.11`composer require elgg/elgg:^1.7.11`

Affected Products

1 product · 1 configurations

Application

elggelgg

≤ 1.7.10

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Elgg through 1.7.10 has XSS

oss-security.openwall.narkive.comNVDNov 2019

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for elgg/elgg, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update elgg/elgg to 1.7.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-2935 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### VULNERABILITY DESCRIPTION The `internalname` parameter is not properly sanitized, which allows attacker to conduct Cross Site Scripting attack. This may allow an attacker to create a specially crafted URL that would execute arbitrary script code in a victim's browser ### PROOF-OF-CONCEPT/EXPLOIT ```http http://localhost/pg/embed/media?internalname=%20%22onmouseover=%22alert%28/XSS/%29%22style=%22width:3000px!important;height:3000px!important;z-index:999999;position:absolute!important;left:0;top:0;%22%20x=%22 ```

O3 Security · Impact-Aware SCA

Is CVE-2011-2935 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

OpenSSF Scorecard

Package health score

Elgg

5.5/10

Maintained10/10

Code-Review10/10

Branch-ProtectionN/A

Assessed Nov 2, 2026

Timeline

First exploit

Nov 13, 2019

Disclosed

Apr 22, 2022

Last updated

Jan 12, 2024

Identifiers

CVE-2011-2935

References

Advisorynvd.nist.gov · CVE 2011 2935 Webgithub.com Webgithub.com · 2843b4f846874d434a2403ac1f27e41035b45e04 Weboss-security.openwall.narkive.com · cve request elgg 1 7 10 multiple vulnerabilities Websecurity-tracker.debian.org · CVE 2011 2935 Webweb.archive.org · elgg 1711 released Webyehg.net · [elgg 1710] xss sqlin Packagegithub.com · Elgg

Related vulnerabilities

Also affects elgg/elgg

This CVE is medium severity; 4 of 4 other CVEs affecting elgg/elgg are rated as high or higher (top: high).

CVE-2019-11016CVE-2021-4072CVE-2021-3980CVE-2021-3964

Same weakness: CWE-79

This CVE is medium severity; 4 of 4 other CVEs with CWE-79 are rated as high or higher (top: critical).

CVE-2026-55649CVE-2026-113787CVE-2026-44267CVE-2026-96632Browse all CWE-79

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedJan 12, 2024