CVE-2026-14871 is a broken object-level authorization vulnerability in osTicket affecting versions 1.18.3 and 1.17.7. The flaw is present in the AJAX ticket-management subsystem, where server-side authorization checks on ticket-related object references are insufficient, resulting in an insecure direct object reference condition. An attacker who can interact with the vulnerable AJAX functionality may be able to reference ticket-related objects outside their authorized scope and perform unauthorized access or manipulation of those objects.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Repository contains a simple Python proof-of-concept for CVE-2026-14871, a Broken Object Level Authorization / IDOR issue in osTicket's staff AJAX handler. Structure is minimal: README.md documents the vulnerability, impact, patch status, and disclosure timeline; exploit.py is the only code file and serves as the entry point. The script uses requests.Session to maintain authenticated state, first fetching /scp/login.php to scrape the __CSRFToken__ value, then posting credentials to authenticate as a low-privileged agent. After login, it sends GET requests to /scp/ajax.php/tickets/{ticket_id}/field/{field_id}/view and treats HTTP 200 as successful unauthorized access, printing extracted field contents after stripping HTML with BeautifulSoup. It also includes a helper to enumerate multiple field IDs for a chosen ticket. The exploit does not achieve code execution; its main capability is authenticated data disclosure and horizontal privilege escalation across department boundaries in vulnerable osTicket deployments. The PoC is operational but basic, with hardcoded lab values (localhost target, agent_a credentials, ticket/field IDs) and no stealth, threading, or generalized automation beyond simple enumeration.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.