How severe is CVE-2011-2718?

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

Which packages are affected by CVE-2011-2718?

CVE-2011-2718 affects the following packages: phpmyadmin/phpmyadmin (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2011-2718?

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

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

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

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

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

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

No public exploit code has been indexed for CVE-2011-2718 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-2011-2718?

CVE-2011-2718 has an EPSS (Exploit Prediction Scoring System) score of 1.7%, placing it in the 77th 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-2718?

CVE-2011-2718 is classified as Path Traversal (CWE-22). 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-2718 published, and has it been updated?

CVE-2011-2718 was published on August 1, 2011 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2011-2718: phpmyadmin — Fixed in 3.4.3.2

EPSS Exploitation Probability

via FIRST.org ↗

1.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs77th percentile — riskier than 77% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐘phpmyadmin/phpmyadmin

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 directory traversal vulnerabilities in the relational schema implementation in phpMyAdmin 3.4.x before 3.4.3.2 allow remote authenticated users to include and execute arbitrary local files via directory traversal sequences in an export type field, related to (1) libraries/schema/User_Schema.class.php and (2) schema_export.php.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`phpmyadmin/phpmyadmin`	≥ 3.4&&< 3.4.3.2	3.4.3.2`composer require phpmyadmin/phpmyadmin:^3.4.3.2`

Affected Products

1 product · 5 configurations

Application

phpmyadminphpmyadmin

5 versions

3.4.0.03.4.1.03.4.2.03.4.3.03.4.3.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for phpmyadmin/phpmyadmin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update phpmyadmin/phpmyadmin to 3.4.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-2718 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

Multiple directory traversal vulnerabilities in the relational schema implementation in phpMyAdmin 3.4.x before 3.4.3.2 allow remote authenticated users to include and execute arbitrary local files via directory traversal sequences in an export type field, related to (1) libraries/schema/User_Schema.class.php and (2) schema_export.php.

O3 Security · Impact-Aware SCA

Is CVE-2011-2718 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2011-2718 — phpmyadmin