Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2010-5029: SQL Injection in Ecomat CMS 5.0 index.php

Published Nov 2, 2011 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v2
EPSS1.2%68th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Codefabrik
IdentifiersCVE-2010-5029CWE-89 · Improper Neutralization of Special…

CVE-2010-5029 is an SQL injection vulnerability in Ecomat CMS 5.0, specifically in the index.php file. The vulnerability allows remote attackers to execute arbitrary SQL commands via the 'show' parameter in a web action. This occurs due to insufficient sanitization of user-supplied input before it is incorporated into SQL queries.

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 execute arbitrary SQL commands against the backend database. This can lead to unauthorized data access, data modification, or deletion, and potentially full compromise of the application and underlying server if further chained with other vulnerabilities.

Mitigation

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

As an immediate mitigation, implement input validation and sanitization for the 'show' parameter to block malicious SQL input. Additionally, use web application firewalls (WAFs) to detect and block SQL injection attempts, and restrict database user privileges to minimize impact in case of exploitation.

Remediation

Patch, then assume compromise.

Upgrade to a fixed version of Ecomat CMS, if available, that properly sanitizes user input. If no patch is available, modify the application code to use parameterized queries or prepared statements for all database access, especially for the 'show' parameter in index.php.

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
CodefabrikEcomat Cmsapplication
FAQ

Frequently asked questions

Is CVE-2010-5029 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2010-5029 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2010-5029?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2010-5029.
Is there a patch for CVE-2010-5029?
Upgrade to a fixed version of Ecomat CMS, if available, that properly sanitizes user input. If no patch is available, modify the application code to use parameterized queries or prepared statements for all database access, especially for the 'show' parameter in index.php.
What products are affected by CVE-2010-5029?
Codefabrik Ecomat Cms.
How severe is CVE-2010-5029?
CVE-2010-5029 has a CVSS v2 score of 7.5 (High) and an EPSS score of 1.2% (68th 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.