Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-100847 – SQL/DQL Injection (Data Exfiltration) – AzuraCast before 0.23.8

Be the first to know when new zero-days emerge:

Summary

CVE-2026-100847 is a DQL (Doctrine Query Language) injection vulnerability in AzuraCast, a self-hosted web radio management suite, affecting all versions before 0.23.8. The flaw resides in the sortOrder API parameter handled by AbstractSearchableListAction.php and allows unauthenticated, network-based attackers to inject arbitrary DQL expressions into backend database queries. Successful exploitation can expose sensitive data such as user credentials and station configuration details, and the issue is rated HIGH severity.

Technical details

  • Root cause: The sortOrder parameter used by AzuraCast’s searchable list API endpoints is passed into a Doctrine ORM query without adequate validation or sanitization, permitting attacker-controlled DQL fragments to be evaluated by the application.
  • Trigger conditions: An attacker sends a crafted value in the sortOrder parameter to an affected API endpoint that extends AbstractSearchableListAction.php; no authentication or user interaction is required to trigger the injection.
  • Attack vector: Remote/network — the vulnerable parameter is reachable over HTTP(S) on any exposed AzuraCast instance.
  • Impact: Unauthorized extraction of sensitive database contents, including user credentials and station configuration/settings, resulting in a confidentiality breach; no direct impact on integrity or availability has been reported.

Affected software

  • AzuraCast versions prior to 0.23.8 (all earlier releases)
  • Fixed in AzuraCast 0.23.8 and later

Severity

  • CVSS v3.1 Base Score: 7.5 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
  • CVSS v4.0 Base Score: 8.7 (High) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade all AzuraCast deployments to version 0.23.8 or later, which contains the fix for the sortOrder DQL injection.
  • If immediate patching is not possible: Restrict or disable public/unauthenticated access to AzuraCast API endpoints that accept a sortOrder parameter (e.g., via reverse proxy or firewall rules), and monitor application and database logs for anomalous or malformed sortOrder values indicative of injection attempts. These are interim compensating controls only — apply the vendor patch as soon as possible.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge