CVE-2022-43515: X-Forwarded-For header is active by default causes access to Zabbix sites in maintenance mode
Noroxi assessment
Priority: Monitor (action score 39/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.2% (FIRST EPSS); higher than 69.6% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: zabbix (Debian:10) 1:4.0.4+dfsg-1+deb10u2; zabbix (Debian:11) 1:5.0.44+dfsg-1+deb11u1; zabbix (Debian:12) 1:6.0.13+dfsg-1.
- Severity is disputed: the assigning authority (CNA) scores it 5.3, NVD 9.8.
Low priority for now. Upgrade to zabbix (Debian:10) 1:4.0.4+dfsg-1+deb10u2; zabbix (Debian:11) 1:5.0.44+dfsg-1+deb11u1; zabbix (Debian:12) 1:6.0.13+dfsg-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Zabbix Frontend provides a feature that allows admins to maintain the installation and ensure that only certain IP addresses can access it. In this way, any user will not be able to access the Zabbix Frontend while it is being maintained and possible sensitive data will be prevented from being disclosed. An attacker can bypass this protection and access the instance using IP address not listed in the defined range.
- Published
- Dec 5, 2022
- Updated
- Jun 17, 2026
- EPSS
- 1.2% · 69th percentile
- CWE
- CWE-20
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.2%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 9.8
- CNA · Zabbix
- 5.3
- 4.5 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| zabbix | frontend | cpe:2.3:a:zabbix:frontend |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- zabbix frontend4.0.0 and later · up to 4.0.44 inclusive
- zabbix frontend5.0.0 and later · up to 5.0.29 inclusive
- zabbix frontend6.0.0 and later · up to 6.0.9 inclusive
- zabbix frontend6.2.0 and later · up to 6.2.4 inclusive
- zabbix frontend5.0.30
- zabbix frontend6.0.11
- zabbix frontend6.2.5
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Zabbix). Independent of NVD's CPE analysis and usually ahead of it.
Zabbix Frontend
- 4.0.0-4.0.44, 5.0.0-5.0.29, 6.0.0-6.0.9, 6.2.0-6.2.4affected
- 5.0.30rc1 and later · before unspecifiednot affected
- 6.0.11rc1 and later · before unspecifiednot affected
- 6.2.5rc1 and later · before unspecifiednot affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:10 | zabbix | before 1:4.0.4+dfsg-1+deb10u2 | 1:4.0.4+dfsg-1+deb10u2 |
| Debian:11 | zabbix | before 1:5.0.44+dfsg-1+deb11u1 | 1:5.0.44+dfsg-1+deb11u1 |
| Debian:12 | zabbix | before 1:6.0.13+dfsg-1 | 1:6.0.13+dfsg-1 |
| SUSE:OpenStack Cloud 9 | zabbix | before 4.0.12-4.21.1 | 4.0.12-4.21.1 |
Same product
zabbix: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-27232Frontend arbitrary file read in oauth.authorize action27Monitor
- CVE-2025-49643Frontend DoS vulnerability due to asymmetric resource consumption24Monitor
- CVE-2023-30958DOM XSS in Developer mode dashboard via redirect GET parameter24Monitor
Published before and after this one in the same product
- ← EarlierCVE-2022-24918Mar 9, 2022 · Reflected XSS in item configuration window of Zabbix Frontend17Monitor
- ← EarlierCVE-2022-24919Mar 9, 2022 · Reflected XSS in graph configuration window of Zabbix Frontend17Monitor
- Later →CVE-2023-29454Jul 13, 2023 · Persistent XSS in the user form21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:zabbix | 1:6.0.13+dfsg-1 · Debian:12 | Package registry (OSV) |
| suse:zabbix | 4.0.12-4.21.1 · SUSE:OpenStack Cloud 9 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.