Wazuh before 4.14.9 SQL Injection via WazuhDBBackend _substitute_params
Wazuh versions from 4.0.0 before 4.14.9 are affected when an authenticated user holds agent:read on one agent and at least two agents are enrolled. Fixed in 4.14.9.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.14.9
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Wazuh versions from 4.0.0 before 4.14.9 Attacker holds agent:read on at least one agent At least two agents enrolled, with one readable by the attacker
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Wazuh security monitoring software from 4.0.0 up to (but not including) the fixed release is affected by a SQL injection flaw in its database backend. A remote attacker who has low-privilege login with read access to one agent can use it to extract the internal keys of all agents.
Read the original description
Wazuh versions from 4.0.0 before 4.14.9 contain a sql injection vulnerability in WazuhDBBackend._substitute_params due to sequential regex placeholder cross-contamination. Authenticated users with agent:read on one agent can inject UNION SELECT via the q and search parameters to extract every agent's internal_key through a blind boolean oracle on total_affected_items.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Wazuh versions from 4.0.0 before 4.14.9 Attacker holds agent:read on at least one agent At least two agents enrolled, with one readable by the attackerUpgrade to a fixed version: 4.14.9.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- wazuh wazuh
From 4.0.0 · fixed in 4.14.9
Evidence 3
- Advisory
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-112341
Is CVE-2026-112341 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An authenticated user with agent:read on one agent can inject UNION SELECT through WazuhDBBackend _substitute_params. Using a blind boolean oracle on total_affected_items, they can extract every enrolled agent's internal_key, bypass RBAC scope restrictions, and run arbitrary SELECT statements against the manager global.db.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-112341?
wazuh: from 4.0.0 before 4.14.9.Source: cve.now feed data
Am I affected, and how do I check?
Wazuh versions from 4.0.0 before 4.14.9 are affected. The bug requires an authenticated user with agent:read on at least one agent, and at least two agents enrolled, with one readable by that user and others not. Compare your installed Wazuh version against the 4.14.9 fix and review which users hold agent:read.Source: vulncheck.com, github.com
How do I fix CVE-2026-112341?
Upgrade Wazuh to 4.14.9 or later, which contains the fix. No workaround is listed in the facts.Source: vulncheck.com, github.com