Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2015-1577: Directory Traversal in u5CMS u5admin/deletefile.php

Published Feb 11, 2015 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.4Medium · v2
EPSS7.3%94th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Yuba
IdentifiersCVE-2015-1577CWE-22 · Improper Limitation of a Pathname…

A directory traversal vulnerability exists in u5CMS before version 3.9.4, specifically in the u5admin/deletefile.php script. The vulnerability allows remote attackers to write to arbitrary files on the server by supplying a crafted value to the 'f' parameter, such as directory traversal sequences (..), or a full pathname. This can be exploited to overwrite or create files outside the intended directory structure.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote attackers to write to arbitrary files on the server, potentially leading to arbitrary code execution, defacement, or denial of service by overwriting critical files.

Mitigation

If you can’t patch tonight, do this now.

Restrict access to u5admin/deletefile.php to trusted users only. Employ web server configuration to block requests containing directory traversal patterns. Monitor and log file operations for suspicious activity.

Remediation

Patch, then assume compromise.

Upgrade u5CMS to version 3.9.4 or later, where this vulnerability has been addressed. Ensure that user-supplied input to file operations is properly sanitized and validated to prevent directory traversal.

Public exploits

Exploits

No validated public exploits yet. Hidden: 2 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
YubaU5cmsapplication
FAQ

Frequently asked questions

Is CVE-2015-1577 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2015-1577 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2015-1577?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2015-1577.
Is there a patch for CVE-2015-1577?
Upgrade u5CMS to version 3.9.4 or later, where this vulnerability has been addressed. Ensure that user-supplied input to file operations is properly sanitized and validated to prevent directory traversal.
What products are affected by CVE-2015-1577?
Yuba U5cms.
How severe is CVE-2015-1577?
CVE-2015-1577 has a CVSS v2 score of 6.4 (Medium) and an EPSS score of 7.3% (94th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.