How severe is CVE-2013-1831?

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

Which packages are affected by CVE-2013-1831?

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

How do I fix CVE-2013-1831?

A fix is available for CVE-2013-1831; 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-2013-1831 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-2013-1831 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2013-1831 actively exploited in the wild?

No public exploit code has been indexed for CVE-2013-1831 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2013-1831?

CVE-2013-1831 has an EPSS (Exploit Prediction Scoring System) score of 1.6%, placing it in the 76th 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-2013-1831?

CVE-2013-1831 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2013-1831 published, and has it been updated?

CVE-2013-1831 was published on May 13, 2022 and was last updated on December 5, 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-2013-1831 — moodle

Fix: moodle/moodle@2c7cdbb

CVE-2013-1831 is a Information Exposure vulnerability in moodle/moodle. A fix is available for moodle/moodle — see the affected versions and patch details below.

Moodle reveals absolute path in exception message

Published

May 13, 2022

Updated

Dec 5, 2024

Affected

4 pkgs

Patched

3 / 4

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs76th percentile — riskier than 76% 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

lib/setuplib.php in Moodle through 2.1.10, 2.2.x before 2.2.8, 2.3.x before 2.3.5, and 2.4.x before 2.4.2 allows remote attackers to obtain sensitive information via an invalid request, which reveals the absolute path in an exception message.

Affected Packages

4 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`moodle/moodle`	all versions	No fix
🐘Packagist	`moodle/moodle`	≥ 2.2.0&&< 2.2.8	2.2.8`composer require moodle/moodle:^2.2.8`
🐘Packagist	`moodle/moodle`	≥ 2.3.0&&< 2.3.5	2.3.5`composer require moodle/moodle:^2.3.5`
🐘Packagist	`moodle/moodle`	≥ 2.4.0&&< 2.4.2	2.4.2`composer require moodle/moodle:^2.4.2`

Affected Products

1 product · 101 configurations

Application

moodlemoodle

101 versions

1.1.11.2.01.2.11.3.01.3.11.3.21.3.31.3.41.4.11.4.21.4.31.4.4

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-2013-1831; 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
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-1831 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works