CVE-2010-5049
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSQL injection vulnerability in events.php in Zabbix 1.8.1 and earlier allows remote attackers to execute arbitrary SQL commands via the nav_time parameter.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSQL injection vulnerability in the nav_time parameter of events.php in Zabbix 1.8.1 and earlier allows remote unauthenticated attackers to execute arbitrary SQL commands by injecting malicious SQL statements through the nav_time parameter.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.8.1= 1.1= 1.1.1= 1.1.2= 1.1.3= 1.1.4= 1.1.5= 1.1.6= 1.1.7= 1.3= 1.3.1= 1.3.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Zabbix versionCheck the Zabbix version by accessing the web frontend login page, checking the footer, or running 'zabbix_server --version' on the server, or inspecting the Zabbix database version tableAffected if The installed version is 1.8.1 or earlier, or matches any of the affected versions: 1.1, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6, 1.1.7, 1.3, 1.3.1, 1.3.2, or 1.8.1
-
Locate events.phpFind the events.php file in the Zabbix web frontend directory, typically under /usr/share/zabbix/ or the web root path where Zabbix is installedAffected if The events.php file exists in the Zabbix web directory and is accessible via HTTP
-
Verify nav_time parameter handlingInspect the events.php source code and search for the nav_time parameter usage; check if it is directly used in SQL queries without proper escaping or parameterized queriesAffected if The nav_time parameter is processed without prepared statements or input sanitization and is directly concatenated into SQL queries
-
Test for SQL injectionSend a crafted request to events.php with a test payload in nav_time such as "' OR '1'='1" and observe if SQL errors are returned or if the query behaves unexpectedlyAffected if The application returns SQL syntax errors or exhibits unexpected behavior indicating unsanitized input is being executed as SQL
You are affected if running Zabbix version 1.8.1 or earlier AND the events.php file with the vulnerable nav_time parameter is accessible and processes user input without parameterized queries.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a patched version of Zabbix (1.8.2 or later) or implement proper input validation and parameterized queries for the nav_time parameter in events.php to prevent SQL injection.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-5049 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2010-5049 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data