Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with low-privileged Znuny account
-
ExploitCraft malicious ContentSearch value
-
ExecutionInject SQL via ticket search query
-
ImpactExfiltrate or modify database records
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated Znuny session (PR:L / AU:Y) with access to ticket-search functionality, and the attacker must be able to supply the ContentSearch parameter, which the application expects to contain only the literal keyword 'AND' or 'OR' but concatenates verbatim into the SQL statement without validation. The flaw affects Znuny versions through 7.3.6 in default configurations of the ticket-search backend (Kernel::System::Ticket::TicketSearch and Kernel::System::Ticket::ArticleSearchIndex::DB), so no non-default feature toggle appears necessary. Limiting factors: exploitation is gated by needing valid credentials (agent or customer account) and reachability of the search interface; it is not exploitable pre-authentication, which bounds the threat to insiders or attackers who can obtain accounts. |
| Impact | This is a credible, actionable priority rather than a paper-tiger high-CVSS issue, though not an emergency. The provided CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) describes a network-reachable, low-complexity flaw requiring only low privileges (PR:L) and no user interaction, with high confidentiality and integrity impact (VC:H/VI:H) - consistent with CWE-89 SQL injection against a backend ticket database. The attack requirement AU:Y (user authentication) and PR:L together confirm that a valid, low-privileged Znuny account is a hard prerequisite, which meaningfully narrows the attacker population to insiders or anyone able to obtain/register an agent or customer account. No EPSS score, SSVC decision, KEV listing, or POC reference was supplied: there is no public exploit identified at time of analysis and no evidence of active exploitation, so urgency rests on the vulnerability's intrinsic severity and ease, not on observed attacks. One signal to reconcile: the vector sets VA:N (no availability impact on the vulnerable system) while the description and the 'Denial Of Service' tag explicitly cite DoS as an outcome - a SQLi that permits data modification can plausibly degrade or destroy the ticket store, so defenders should treat availability as at-risk despite the VA:N scoring. Net: patch promptly given the low exploitation barrier, but absent KEV/EPSS/POC this is a standard-priority authenticated SQLi, not a drop-everything internet-worm scenario. |
| Exploit ScenarioDerived | A low-privileged Znuny agent or customer user with access to the ticket-search functionality submits a crafted ContentSearch parameter value that breaks out of the expected 'AND'/'OR' keyword and injects arbitrary SQL into the generated ticket-search query. Because the input is concatenated directly into the statement (TicketSearch / ArticleSearchIndex::DB), the attacker can read other tenants' tickets, alter records, or issue destructive statements. No public proof-of-concept was provided, but the trivial AND/OR injection point makes exploitation straightforward for anyone with a valid account. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 15, 2026
SQL injection in Znuny's ticket-search backend (versions through 7.3.6) allows an authenticated remote attacker with a valid agent or customer account to inject arbitrary SQL through the ContentSearch parameter, enabling theft or modification of ticketing data. The flaw requires the attacker to reach the search interface and supply a value for a parameter that the code expects to contain only the literal 'AND' or 'OR', yet concatenates verbatim into the generated query (CWE-89). No public exploit code was identified at the time of analysis and no CISA KEV listing applies; the assessed impact is high confidentiality and integrity loss with no confirmed availability impact.
RemediationAI
Patch available per vendor advisory ZSA-2026-15 (https://www.znuny.org/en/advisories/zsa-2026-15); no exact fixed version number is supplied in the available input data, so confirm the specific release in that advisory and upgrade beyond the affected 'through 7.3.6' range. Because exploitation requires a valid agent or customer account, reduce exposure by auditing and pruning unnecessary accounts, enforcing MFA where supported, and limiting search-interface access to trusted users - side effect: this tightens usability for legitimate staff. If an immediate upgrade is not possible, consider a reverse proxy or WAF rule that rejects unexpected ContentSearch values that are not exactly 'AND' or 'OR' - side effect: brittle, may break integrations or miss encoded payloads; additionally restrict the database account used by Znuny to the least privilege needed for normal operation (no DDL, no cross-schema reads) - side effect: may break maintenance tasks or reporting features that rely on broader grants. Log and alert on anomalous search queries and database errors for detection while remediation is in progress.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Znuny is an open-source fork of the OTRS helpdesk/ticketing platform, written primarily in Perl and backed by a relational database. The vulnerable code lives in Kernel::System::Ticket::TicketSearch and Kernel::System::Ticket::ArticleSearchIndex::DB, where the ContentSearch parameter - intended to act as a boolean keyword ('AND' or 'OR') when composing search SQL - is interpolated directly into the query string rather than bound through placeholders. This is a classic CWE-89 SQL injection: the application fails to neutralize special elements, so characters such as quotes and SQL syntax flow into the database engine and can alter the statement's structure. CPE cpe:2.3:a:znuny:znuny:*:*:*:*:*:*:*:* identifies the affected product family, and the description scopes affected releases to Znuny through 7.3.6. Exploitation requires an authenticated session (CVSS PR:L, AU:Y in the supplied vectors) with access to ticket search; no non-default configuration toggle appears necessary, so default deployments that expose the search UI to logged-in users are in scope.
Know when Znuny gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:L/SI:L/SA:N/AU:Y/R:U/RE:M/U:Amber
Network-reachable search with a trivial AND/OR injection gives AV:N/AC:L; a valid low-privileged account is required so PR:L; high data read/modify yields C:H/I:H, A:N kept to match the vendor vector's VA:N.
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
Lifecycle Timeline
2DescriptionCVE.org
Znuny through 7.3.6 constructs a ticket-search database query by directly concatenating user-supplied input into the SQL statement. This lack of proper sanitization or the use of parameterized queries allows an attacker to inject arbitrary SQL commands, leading to data theft, modification, or denial of service. Specifically this is in Kernel::System::Ticket::TicketSearch and Kernel::System::Ticket::ArticleSearchIndex::DB via the ContentSearch parameter. The parameter is expected to be either "AND" or "OR", but its value was concatenated directly into the generated SQL query without validation.
Executive ViewAI
Znuny's ticket-search backend (versions through 7.3.6) is affected by a SQL injection flaw reachable through the ContentSearch parameter, allowing someone holding a valid agent or customer account to read or alter ticketing records; no vendor patch is currently available. Helpdesk systems typically concentrate sensitive customer, employee, and incident information, so exposure means potential disclosure of that data plus falsified, altered, or deleted tickets that can erode service continuity and audit integrity. Leadership should prioritize this for any team running Znuny, because near-term risk reduction depends entirely on access restrictions, monitoring, and configuration hardening rather than a fix.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict or disable ticket search for customer and non-essential agent accounts; enforce a web application firewall or reverse-proxy rule that only permits the expected 'AND'/'OR' literal in ContentSearch and logs all other values; apply least privilege to the Znuny database account so injected queries cannot read or write beyond ticketing tables; enable and monitor search-endpoint logging for anomalous ContentSearch payloads and unusual ticket data access or modification; verify backup and restore integrity to recover from tampering; and monitor the vendor advisory for a patched release.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
An Eval Injection issue was discovered in Znuny through 7.1.3. Rated critical severity (CVSS 9.8), this vulnerability is
An issue was discovered in Znuny before 7.1.4. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploi
An issue was discovered in Znuny through 7.1.3. Rated critical severity (CVSS 9.8), this vulnerability is remotely explo
An issue was discovered in Znuny and Znuny LTS 6.0.31 through 6.5.7 and Znuny 7.0.1 through 7.0.16 where a logged-in use
Authentication bypass in Znuny through 7.3.6 allows a remote, unauthenticated attacker to impersonate any existing accou
An issue was discovered in Znuny LTS 6.5.1 through 6.5.7 and Znuny 7.0.1 through 7.0.16 where a logged-in agent is able
An issue was discovered in Znuny before 7.1.5. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitabl
An issue was discovered in Znuny through 7.1.3. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitab
Znuny before LTS 6.5.1 through 6.5.10 and 7.0.1 through 7.0.16 allows DoS/ReDos via email. Rated high severity (CVSS 7.5
An issue was discovered in Znuny 7.0.1 through 7.0.16 where the ticket detail view in the customer front allows the exec
Reflected cross-site scripting in Znuny's AdminCommunicationLog (communication log administration view) allows a low-pri
An issue was discovered in Znuny through 6.5.14 and 7.x through 7.1.6. Rated medium severity (CVSS 6.1), this vulnerabil
EUVD-2026-101821
GHSA-mxcg-m44c-38cw
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB