How severe is CVE-2015-2269?

No CVSS score has been assigned to CVE-2015-2269 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2015-2269?

CVE-2015-2269 affects the following packages: moodle/moodle (Packagist), moodle/moodle (Packagist), moodle/moodle (Packagist), moodle/moodle (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2015-2269?

A fix is available for CVE-2015-2269; check the affected-versions list above or the advisory for the patched release of moodle/moodle, then make sure no transitive dependency still pins the vulnerable range.

How do I detect CVE-2015-2269 in my Packagist dependencies?

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

How do I mitigate CVE-2015-2269 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-2015-2269 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2015-2269, including 1 documented proof-of-concept exploit on Exploit-DB. 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-2015-2269?

CVE-2015-2269 has an EPSS (Exploit Prediction Scoring System) score of 3.3%, placing it in the 88th 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-2015-2269?

CVE-2015-2269 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-2015-2269 published, and has it been updated?

CVE-2015-2269 was published on May 13, 2022 and was last updated on December 8, 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

CVE-2015-2269 — moodle

Fix: moodle/moodle@ead8b28

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

Moodle XSS Vulnerability

Published

May 13, 2022

Updated

Dec 8, 2024

Affected

4 pkgs

Patched

3 / 4

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

3.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs88th percentile — riskier than 88% of all scored CVEsHighest risk

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

Real-World Exposure

4 pkgs affected

🐘moodle/moodle🐘moodle/moodle🐘moodle/moodle🐘moodle/moodle

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

Multiple cross-site scripting (XSS) vulnerabilities in lib/javascript-static.js in Moodle through 2.5.9, 2.6.x before 2.6.9, 2.7.x before 2.7.6, and 2.8.x before 2.8.4 allow remote authenticated users to inject arbitrary web script or HTML via a (1) alt or (2) title attribute in an IMG element.

Affected Packages

4 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`moodle/moodle`	all versions	No fix
🐘Packagist	`moodle/moodle`	≥ 2.6.0&&< 2.6.9	2.6.9`composer require moodle/moodle:^2.6.9`
🐘Packagist	`moodle/moodle`	≥ 2.7.0&&< 2.7.6	2.7.6`composer require moodle/moodle:^2.7.6`
🐘Packagist	`moodle/moodle`	≥ 2.8.0&&< 2.8.4	2.8.4`composer require moodle/moodle:^2.8.4`

Affected Products

1 product · 29 configurations

Application

moodlemoodle

≤ 2.5.9

28 versions

2.5.02.5.12.5.22.5.32.5.42.5.52.5.62.5.72.5.82.6.02.6.12.6.2

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.

EDB-36418webappsphp

Moodle 2.5.9/2.6.8/2.7.5/2.8.3 - Block Title Handler Cross-Site Scripting

by LiquidWorm · Mar 17, 2015

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for moodle/moodle, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
A fix is available for CVE-2015-2269; check the affected-versions list above or the advisory for the patched release of moodle/moodle, then make sure no transitive dependency still pins the vulnerable range.
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.