LiveActive security incident?Get immediate response
CVE Record

CVE-2013-5743: Multiple SQL injection vulnerabilities in Zabbix 1.8.x before 1.8.18rc1, 2.0.x before 2.0.9rc1, and 2.1.x b...

Multiple SQL injection vulnerabilities in Zabbix 1.8.x before 1.8.18rc1, 2.0.x before 2.0.9rc1, and 2.1.x before 2.1.7.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2013-5743 covers multiple SQL injection flaws in older Zabbix releases. SQL injection can let an attacker interfere with database-backed application behavior or access data, depending on reachability and privileges. The provided sources do not include a CVSS score, exploit evidence, or detailed impact description.

Executive priority

Treat this as a legacy-asset risk. It is important if old Zabbix remains in production, especially where monitoring systems have broad visibility, but urgency cannot be scored from the provided sources alone.

Technical view

The CVE description names affected Zabbix branches: 1.8.x before 1.8.18rc1, 2.0.x before 2.0.9rc1, and 2.1.x before 2.1.7. References include Fedora package updates and Zabbix issue ZBX-7091. No CWE, CVSS vector, vulnerable endpoint list, or exploitation details are provided.

Likely exposure

Exposure is limited to environments still running the named legacy Zabbix branches or related distribution packages. Modern supported Zabbix deployments are not identified as affected in the provided bundle.

Exploitation context

The source bundle does not show active exploitation, and the CVE is not marked in KEV. It also does not provide public exploit status, attack prerequisites, authentication requirements, or affected endpoints.

Researcher notes

Evidence is sparse. The CVE record names affected branches and references ZBX-7091 plus Fedora updates, but lacks endpoint, parameter, authentication, CVSS, and exploitability detail. Validate exposure through version/package inventory before deeper testing.

Mitigation direction

  • Inventory Zabbix versions across servers and packaged deployments.
  • Upgrade affected branches beyond the listed vulnerable version ranges.
  • Apply relevant Fedora zabbix or zabbix20 package updates where applicable.
  • Check Zabbix issue ZBX-7091 and vendor guidance for exact remediation details.
  • Reduce unnecessary exposure to Zabbix management services until remediation is verified.

Validation and detection

  • Confirm no deployment runs Zabbix 1.8.x before 1.8.18rc1.
  • Confirm no deployment runs Zabbix 2.0.x before 2.0.9rc1.
  • Confirm no deployment runs Zabbix 2.1.x before 2.1.7.
  • Map installed OS packages against the referenced Fedora update records.
  • Document exceptions where legacy Zabbix cannot be upgraded immediately.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2013-5743 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.