CVE-2013-7341 — moodle/moodle
Fix: moodle/moodle@98d135fCVE-2013-7341 is a Cross-site Scripting (XSS) vulnerability in moodle/moodle. A fix is available for moodle/moodle — see the affected versions and patch details below.
Moodle cross-site scripting (XSS) vulnerabilities
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
moodle/moodle🐘moodle/moodle🐘moodle/moodle🐘typo3/cms🐘typo3/cmsReal-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 Flowplayer Flash before 3.2.17, as used in Moodle through 2.3.11, 2.4.x before 2.4.9, 2.5.x before 2.5.5, and 2.6.x before 2.6.2, allow remote attackers to inject arbitrary web script or HTML by (1) providing a crafted playerId or (2) referencing an external domain, a related issue to CVE-2013-7342.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | moodle/moodle | all versions | 2.4.9composer require moodle/moodle:^2.4.9 |
| 🐘Packagist | moodle/moodle | ≥ 2.5.0&&< 2.5.5 | 2.5.5composer require moodle/moodle:^2.5.5 |
| 🐘Packagist | moodle/moodle | ≥ 2.6.0&&< 2.6.2 | 2.6.2composer require moodle/moodle:^2.6.2 |
| 🐘Packagist | typo3/cms | ≥ 6.2.0&&< 6.2.14 | 6.2.14composer require typo3/cms:^6.2.14 |
| 🐘Packagist | typo3/cms | ≥ 7.0.0&&< 7.3.1 | 7.3.1composer require typo3/cms:^7.3.1 |
Detection & mitigation playbook
Open-source dependencyDetect
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
Update moodle/moodle to 2.4.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-7341 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2013-7341 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2013-7341. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2013-7341 in your dependencies?
O3 Security finds CVE-2013-7341 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.