Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2010-1474: Directory Traversal in Sweety Keeper Joomla! Component

Published Apr 19, 2010 · 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.8Medium · v2
EPSS9.5%96th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Supachai Teasakul
IdentifiersCVE-2010-1474CWE-22 · Improper Limitation of a Pathname…

CVE-2010-1474 is a directory traversal vulnerability in the Sweety Keeper (com_sweetykeeper) component version 1.5.x for Joomla!. The vulnerability exists due to insufficient sanitization of the 'controller' parameter in requests to index.php, allowing remote attackers to inject directory traversal sequences (..) and access arbitrary files on the server.

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 read arbitrary files on the server, which may include sensitive configuration files, credentials, or other data. Depending on server configuration and file contents, this could lead to further compromise or information disclosure.

Mitigation

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

Restrict access to the vulnerable component, use web application firewalls to block directory traversal patterns, and ensure that the web server runs with the least privileges necessary to limit the impact of a successful attack.

Remediation

Patch, then assume compromise.

Upgrade or patch the Sweety Keeper component to a version that properly sanitizes user input in the 'controller' parameter. If no patch is available, consider removing or disabling the vulnerable component.

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
Supachai TeasakulCom Sweetykeeperapplication
FAQ

Frequently asked questions

Is CVE-2010-1474 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2010-1474 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2010-1474?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2010-1474.
Is there a patch for CVE-2010-1474?
Upgrade or patch the Sweety Keeper component to a version that properly sanitizes user input in the 'controller' parameter. If no patch is available, consider removing or disabling the vulnerable component.
What products are affected by CVE-2010-1474?
Supachai Teasakul Com Sweetykeeper.
How severe is CVE-2010-1474?
CVE-2010-1474 has a CVSS v2 score of 6.8 (Medium) and an EPSS score of 9.5% (96th 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.