How severe is CVE-2015-4180?

CVE-2015-4180 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2015-4180 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (85th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2015-4180?

CVE-2015-4180 primarily affects Phpmybackuppro. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2015-4180?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2015-4180 published?

CVE-2015-4180 was published on 2017-08-25 and last updated on 2026-06-17.

CVE-2015-4180

CVE-2015-4180 is a high-severity vulnerability in Phpmybackuppro with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-22.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v2: 5.0
EPSS exploit prediction: 3% (85th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-22
Affected product: Phpmybackuppro
Published: 2017-08-25
Last modified: 2026-06-17

Description

Directory traversal vulnerability in get_file.php in phpMyBackupPro 2.1 through 2.4 allows remote attackers to read arbitrary files via a .. (dot dot) in the view parameter. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information. NOTE: this vulnerability exists due to an incomplete fix to CVE-2009-4050.

Frequently asked questions

What is CVE-2015-4180?: Directory traversal vulnerability in get_file.php in phpMyBackupPro 2.1 through 2.4 allows remote attackers to read arbitrary files via a .. (dot dot) in the view parameter. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information. NOTE: this vulnerability exists due to an incomplete fix to CVE-2009-4050.
How severe is CVE-2015-4180?: CVE-2015-4180 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2015-4180 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (85th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2015-4180?: CVE-2015-4180 primarily affects Phpmybackuppro. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2015-4180?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2015-4180 published?: CVE-2015-4180 was published on 2017-08-25 and last updated on 2026-06-17.

References

http://www.openwall.com/lists/oss-security/2015/06/04/10

Affected products (4)

cpe:2.3:a:phpmybackuppro:phpmybackuppro:2.1:*:*:*:*:*:*:*
cpe:2.3:a:phpmybackuppro:phpmybackuppro:2.2:*:*:*:*:*:*:*
cpe:2.3:a:phpmybackuppro:phpmybackuppro:2.3:*:*:*:*:*:*:*
cpe:2.3:a:phpmybackuppro:phpmybackuppro:2.4:*:*:*:*:*:*:*

More vulnerabilities in Phpmybackuppro

CVE-2015-3639 — High (CVSS 8.8): phpMyBackupPro 2.5 and earlier does not properly sanitize input strings, which allows remote authenticated users to…
CVE-2015-3638 — High (CVSS 8.8): phpMyBackupPro before 2.5 does not validate integer input, which allows remote authenticated users to execute arbitrary…
CVE-2015-3637 — High (CVSS 8.1): SQL injection vulnerability in phpMyBackupPro when run in multi-user mode before 2.5 allows remote attackers to execute…
CVE-2015-4181 — High (CVSS 7.5): Directory traversal vulnerability in get_file.php in phpMyBackupPro 2.1 through 2.5 allows remote attackers to read…
CVE-2015-3640 — High (CVSS 7.5): phpMyBackupPro 2.5 and earlier does not properly escape the "." character in request parameters, which allows remote…
CVE-2024-5415 — High (CVSS 7.1): A vulnerability have been discovered in PhpMyBackupPro affecting version 2.3 that could allow an attacker to execute…

All CVEs affecting Phpmybackuppro →

Other CWE-22 (Path Traversal) vulnerabilities

CVE-2026-48282 — Critical (CVSS 10.0): ColdFusion versions 2025.9, 2023.20 and earlier are affected by an Improper Limitation of a Pathname to a Restricted…
CVE-2026-54917 — Critical (CVSS 10.0): SeaweedFS is a distributed storage system for object storage (S3), file systems, and Iceberg tables. Prior to 4.30, the…
CVE-2026-11429 — Critical (CVSS 10.0): Two endpoints in the Vault Service ScriptsController, shared by Altium Enterprise Server and Altium 365, accept file…
CVE-2026-34909 — Critical (CVSS 10.0): A malicious actor with access to the network could exploit a Path Traversal vulnerability found in UniFi OS devices to…
CVE-2026-7411 — Critical (CVSS 10.0): In Eclipse BaSyx Java Server SDK versions prior to 2.0.0-milestone-10, inadequate path normalization in the Submodel…
CVE-2026-36767 — Critical (CVSS 10.0): A path traversal vulnerability in the /content/images/add endpoint of shopizer v3.2.5 allows attackers write arbitrary…

Browse all CWE-22 (Path Traversal) vulnerabilities →