Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2012-2919: Directory Traversal in Chevereto 1.9.1 Upload/engine.php

Published May 21, 2012 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.0Medium · v2
EPSS3.3%89th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Chevereto
IdentifiersCVE-2012-2919CWE-22 · Improper Limitation of a Pathname…

A directory traversal vulnerability exists in Chevereto 1.9.1, specifically in Upload/engine.php, where the 'v' parameter is not properly sanitized. This allows remote attackers to determine the existence of arbitrary files on the server by supplying directory traversal sequences (..).

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.

An attacker can use this vulnerability to probe for the existence of files outside the intended directory, potentially exposing sensitive information about the server's file structure and the presence of specific files. This can aid in further attacks such as information disclosure or targeted exploitation.

Mitigation

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

As an interim measure, implement input validation and sanitization on the 'v' parameter to block directory traversal patterns. Restrict web server permissions to limit file access and consider using web application firewalls to detect and block suspicious requests.

Remediation

Patch, then assume compromise.

Upgrade to a version of Chevereto where input validation is properly implemented for the 'v' parameter in Upload/engine.php, ensuring that directory traversal sequences are filtered or rejected. Apply any vendor-supplied patches addressing this issue.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 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
CheveretoCheveretoapplication
FAQ

Frequently asked questions

Is CVE-2012-2919 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2012-2919 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2012-2919?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2012-2919.
Is there a patch for CVE-2012-2919?
Upgrade to a version of Chevereto where input validation is properly implemented for the 'v' parameter in Upload/engine.php, ensuring that directory traversal sequences are filtered or rejected. Apply any vendor-supplied patches addressing this issue.
What products are affected by CVE-2012-2919?
Chevereto.
How severe is CVE-2012-2919?
CVE-2012-2919 has a CVSS v2 score of 5.0 (Medium) and an EPSS score of 3.3% (89th 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.