☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]

CVE-2024-41802

CVE-2024-41802 SQL Injection in Xibo
📅 PUBLISHED: 2024-07-30 15:49 UTC 🔄 UPDATED: 2026-09-23 20:16 UTC
[ OFFICIAL PATCH DEPLOYED ↓ ] FIX: LIKELY — 2 independent sources confirm fix
[ DEFENSE PATCH ↓ ]
💣 PoC: None
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🎯 EPSS: 0.46%
👁️
0.46% probability
11.4× above the median CVE
Tier: ELEVATED
30-day exploitation window · FIRST.org · updated daily
Patch available — upgrade to latest release
CVSS SEVERITY SCALE
9.0–10.0 CRITICAL
7.0–8.9 HIGH
4.0–6.9 MEDIUM
0.1–3.9 LOW
0.0 NONE
8.1
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2024-41802 is a critical SQL injection vulnerability discovered in the Xibo Content Management System (CMS). The flaw resides in the API routes responsible for filtering DataSets, allowing an authenticated attacker to inject malicious SQL queries. This enables unauthorized access to and modification of arbitrary data within the Xibo database. The vulnerability is particularly dangerous because it requires only low-privilege authentication, and the impact includes complete compromise of data confidentiality and integrity. The vendor has released patches in versions 3.3.12 and 4.0.14. No public proof-of-concept or exploit code is currently available, but the risk remains high due to the nature of the vulnerability.

⚡ AUTOMATE YOUR CVE INTELLIGENCE

This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.

›Patch confidence — UNVERIFIED to CONFIRMED, cross-referenced NVD + RHSA + Debian
›Exploit & PoC — poc_status, poc_url, has_exploit. Not in NVD.
›Shodan dorks — ready-made queries to find exposed vulnerable systems
›Detection rules — YARA · Wazuh · Elastic (all plans) · Sigma (Pro)
›pending_fields — know exactly which of 7 fields NVD hasn't processed yet
›Free backfill — data incomplete when you paid? Re-check within 30 days = 0 credits
PAYG €0.08/lookup Standard €19/mo (was €29) · 5k credits Pro €65/mo (was €99) · 20k credits FOUNDING PRICE · LOCKED FOR LIFE · ENDS 31 DEC 2026
[ FROM €19/MO ]
Free sandbox key available
No signup required

Supply Chain & Package Security

Xibo is a PHP-based CMS. The vulnerability is in the core application code, not in a third-party package. However, organizations using Xibo should verify the integrity of their installation and ensure no malicious modifications have been made. The supply chain risk is low, but the application itself is the attack vector.

CVSS Breakdown & Threat Level

  • CVSS Score: 8.1 (High)
  • Attack Vector: Network (AV:N)
  • Attack Complexity: Low (AC:L)
  • Privileges Required: Low (PR:L)
  • User Interaction: None (UI:N)
  • Scope: Unchanged (S:U)
  • Confidentiality Impact: High (C:H)
  • Integrity Impact: High (I:H)
  • Availability Impact: None (A:N)

The threat level is High due to the low complexity and the ability to achieve full data compromise with only low-level authentication.

Deep Dive & Mechanics

The vulnerability exists in the API endpoints that handle importing JSON data and importing Layouts containing DataSet data. The Xibo CMS uses SQL queries to filter and process DataSet information. The flaw occurs because user-supplied input is not properly sanitized before being incorporated into these SQL queries.

An authenticated attacker can craft a malicious payload within the JSON data or Layout import. This payload, when processed by the vulnerable API, is injected into the SQL query, allowing the attacker to execute arbitrary SQL commands. The attacker can then extract sensitive data (e.g., user credentials, configuration data) or modify database records (e.g., escalate privileges, deface content).

The vulnerability is specifically in the filtering logic of the DataSet API routes. The code likely uses string concatenation or inadequate parameterized queries, allowing the injection.

Vulnerable vs. Patched Code

Vulnerable Code (Conceptual):

// Vulnerable: Direct concatenation of user input
$filter = $_POST['filter'];
$query = "SELECT * FROM dataset WHERE name = '" . $filter . "'";
$result = $db->query($query);

Patched Code (Conceptual):

// Patched: Use of parameterized queries
$filter = $_POST['filter'];
$stmt = $db->prepare("SELECT * FROM dataset WHERE name = :filter");
$stmt->bindParam(':filter', $filter);
$stmt->execute();
$result = $stmt->fetchAll();

The patched version uses prepared statements with bound parameters, which prevents SQL injection by separating SQL logic from user data.

Exploitation & Lab Setup

Red Team (Offensive)

Lab Setup:

  1. Deploy a vulnerable Xibo CMS instance (version < 3.3.12 or < 4.0.14) in a controlled environment.
  2. Obtain a low-privilege user account (e.g., via registration or default credentials).
  3. Identify the vulnerable API endpoint (e.g., /api/dataset/import or /api/layout/import).

Exploitation Steps:

  1. Authenticate to the Xibo CMS and obtain a session token.
  2. Craft a malicious JSON payload with SQL injection in the filter parameter.
    {
      "filter": "1' OR '1'='1",
      "data": "..."
    }
    
  3. Send the payload to the vulnerable API endpoint.
    curl -X POST -H "Authorization: Bearer <token>" -H "Content-Type: application/json" -d '{"filter": "1'"'"' OR '"'"'1'"'"'='"'"'1", "data": "..."}' http://target/api/dataset/import
    
  4. Observe the response for data exfiltration or error messages indicating successful injection.
  5. Use SQL injection to extract data (e.g., UNION SELECT to retrieve user credentials).

Note: No public exploit code is available. The above is a conceptual example.

Blue Team (Defensive)

Detection:

  • Monitor API logs for unusual SQL-like patterns in request parameters (e.g., OR, UNION, SELECT, --).
  • Look for repeated failed authentication attempts followed by successful exploitation.
  • Use WAF rules to block SQL injection patterns.

Hunting:

  • Search for requests to /api/dataset/import or /api/layout/import with suspicious payloads.
  • Analyze database logs for unexpected queries or errors.

Response:

  • Immediately isolate affected systems.
  • Review database logs for unauthorized access or modifications.
  • Apply the patch or upgrade to a fixed version.

Indicators of Compromise (IOCs)

  • Network:
    • HTTP requests to /api/dataset/import or /api/layout/import containing SQL keywords (e.g., OR, UNION, SELECT, --).
    • Unusual response sizes or error messages containing SQL syntax.
  • Host:
    • Unexpected database queries in logs.
    • New user accounts or privilege escalations.
    • Modified DataSet or Layout records.
  • File:
    • Suspicious JSON files with SQL injection payloads.

Detection Engineering

YARA Rule

rule CVE_2024_41802_Xibo_SQLi {
    meta:
        description = "Detects SQL injection attempts targeting Xibo CMS CVE-2024-41802"
        author = "Valters IT"
        date = "2024-01-01"
        reference = "CVE-2024-41802"
    strings:
        $s1 = "/api/dataset/import" nocase
        $s2 = "/api/layout/import" nocase
        $s3 = "OR" nocase
        $s4 = "UNION" nocase
        $s5 = "SELECT" nocase
        $s6 = "--" nocase
    condition:
        any of ($s1, $s2) and any of ($s3, $s4, $s5, $s6)
}

Sigma Rule

title: Xibo CMS SQL Injection Attempt (CVE-2024-41802)
id: xibo-sqli-cve-2024-41802
status: experimental
description: Detects SQL injection attempts against Xibo CMS API endpoints
author: Valters IT
logsource:
    category: webserver
    product: apache
detection:
    selection:
        cs-method: 'POST'
        cs-uri-query|contains:
            - '/api/dataset/import'
            - '/api/layout/import'
        cs-uri-query|contains|all:
            - 'OR'
            - 'UNION'
            - 'SELECT'
            - '--'
    condition: selection
falsepositives:
    - Legitimate use of SQL keywords in data
level: high

Suricata Rule

alert http $HOME_NET any -> $EXTERNAL_NET any (msg:"Xibo CMS SQL Injection Attempt (CVE-2024-41802)"; flow:to_server,established; content:"POST"; http_method; content:"/api/dataset/import"; http_uri; content:"OR"; http_client_body; content:"UNION"; http_client_body; content:"SELECT"; http_client_body; content:"--"; http_client_body; classtype:web-application-attack; sid:1000001; rev:1;)

Remediation & Mitigation

Immediate Actions:

  1. Upgrade Xibo CMS to version 3.3.12 or 4.0.14 immediately.
  2. If upgrade is not possible, disable the vulnerable API endpoints temporarily.
  3. Review database logs for any signs of exploitation.

Long-term Mitigations:

  • Implement a Web Application Firewall (WAF) with SQL injection rules.
  • Enforce strict input validation and parameterized queries in all API endpoints.
  • Conduct regular security audits and penetration testing.
  • Monitor for new patches and advisories from Xibo.

Compromise Assessment:

  • Check for unauthorized database changes.
  • Review user accounts for privilege escalation.
  • Scan for backdoors or webshells.

Valters IT

◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2024-41802/ · CVE data: NVD/MITRE (public domain) · © 2026 ValtersIT Hub
>_ SYSTEM_CORE: INTEL_ACTIVE
90% TEAM-CURATED // 10% AUTOMATED INGESTION.
ALL PATCH REFERENCES AND VERSION DATA SOURCED FROM NVD + OSV OFFICIAL REGISTRIES.