Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2024-34193: Path Traversal in smanga 3.2.7

Published May 20, 2024 · Updated 11 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS7.5High · v3.1
EPSS1.8%79th percentile
CISA KEVNoNot listed
In the wildReported2 exploitation records in Mallory
Vendors
PocketmangaLkw199711
IdentifiersCVE-2024-34193CWE-22 · Improper Limitation of a Pathname…

smanga 3.2.7 contains a path traversal vulnerability in its PHP file-retrieval interface. The interface does not adequately filter the file parameter, allowing attacker-controlled paths to escape the intended directory and enabling arbitrary file reading.

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 can disclose files outside the intended retrieval directory, subject to the application's filesystem permissions. Exposed files could include sensitive application configuration, credentials, or other locally stored information. Write access and code execution are not established.

Mitigation

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

If immediate patching is not possible, restrict access to the vulnerable interface, especially from untrusted networks. Deploy web application firewall rules or reverse-proxy filtering to block traversal patterns and encoded variants in the file parameter. Reduce the filesystem privileges of the web server/PHP process, segregate sensitive files from web-accessible application paths, and monitor logs for suspicious requests targeting get_file_flow.php with traversal payloads.

Remediation

Patch, then assume compromise.

Upgrade to a fixed version of smanga if one is available from the vendor. In code, remediate by strictly validating and sanitizing the file parameter, rejecting traversal sequences such as ../ and equivalent encodings, and enforcing an allowlist of permitted files or directories. Resolve requested paths with canonicalization and verify they remain within an intended base directory before access. Avoid directly passing user-controlled input to filesystem operations.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
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
Lkw199711Smangaapplication
PocketmangaSmangaapplication
FAQ

Frequently asked questions

Is CVE-2024-34193 exploited in the wild?
Yes. As of Nov 11, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2024-34193?
Yes. As of Nov 11, 2026, Mallory has reports of a public exploit for CVE-2024-34193.
Is there a patch for CVE-2024-34193?
Upgrade to a fixed version of smanga if one is available from the vendor. In code, remediate by strictly validating and sanitizing the file parameter, rejecting traversal sequences such as ../ and equivalent encodings, and enforcing an allowlist of permitted files or directories.
What products are affected by CVE-2024-34193?
Pocketmanga Smanga and Lkw199711 Smanga.
How severe is CVE-2024-34193?
CVE-2024-34193 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 1.8% (79th percentile) as of Nov 11, 2026.
Activity feed

Recent activity

3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
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 signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.