Security readout for executives and security teams
Plain-English summary
A malicious backup could cause AzuraCast’s restore process to execute attacker-controlled SQL. The source reports potential privilege escalation and complete confidentiality, integrity, and availability impact. The delivery path and required restore workflow are not fully documented, so practical exposure depends on who can supply backups and trigger restoration.
Executive priority
Treat this as an urgent investigation and containment issue because the reported maximum impact is system-wide. Immediately identify affected instances and protect backup workflows. Do not claim compromise solely from version presence; active exploitation is not established by the supplied evidence.
Technical view
Versions through 0.23.7 reportedly execute an extracted backup’s db.sql file without validating or sanitizing its contents. This is classified as CWE-89 with CVSS 3.1 score 9.8 (network-accessible, low complexity, no privileges or user interaction). However, the supplied record does not explain how a remote attacker reaches the restore command.
Likely exposure
Potentially exposed organizations are those running AzuraCast 0.23.7 or earlier, especially where untrusted parties can upload, replace, or influence backup archives. The supplied structured affected-product field is unspecified, so asset owners should confirm applicability against vendor guidance before concluding exposure.
Exploitation context
Public proof-of-concept references are listed, indicating technical details may be available. The CVE is not identified as CISA KEV in the supplied bundle, and no cited evidence establishes active exploitation. Real-world exploitability remains partly uncertain because the backup-delivery and restore-trigger conditions are not described.
Researcher notes
The record describes unsanitized execution of db.sql during azuracast:restore, but omits the archive-ingestion path, trigger prerequisites, and official remediation. It also lists vendor, product, and versions as unspecified despite naming versions through 0.23.7. These gaps limit confident reachability analysis and warrant vendor confirmation.
Mitigation direction
- Check current AzuraCast vendor guidance for an official fixed version or mitigation.
- Prevent untrusted users from supplying, replacing, or controlling backup archives.
- Restrict backup restoration to authorized administrators and trusted storage locations.
- Review backup integrity and provenance before any restoration.
- Prioritize isolation or compensating controls until official remediation is confirmed.
Validation and detection
- Inventory AzuraCast instances and identify versions 0.23.7 or earlier.
- Determine who can upload, modify, or select backup archives.
- Review access controls protecting backup storage and restoration operations.
- Audit recent restorations and investigate unexpected privilege or database changes.
- Confirm remediation status against current vendor guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-67917 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/luoxuanxi/SQL-Injection-PoCCVE reference, mitre
- https://github.com/luoxuanxi/SQL-Injection-PoC/tree/main/SQL-Injection-PoCCVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command
Improper Neutralization of Special Elements used in an SQL Command represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.