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

CVE-2024-2568

CVE-2024-2568 SQL Injection in Heyewei
📅 PUBLISHED: 2024-03-17 23:00 UTC 🔄 UPDATED: 2026-09-23 20:34 UTC
[ ZERO-DAY / UNPATCHED ] [ DEFENSE PATCH ↓ ]
💣 PoC: None
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🎯 EPSS: 0.70%
👁️
0.70% probability
17.4× above the median CVE
Tier: ELEVATED
30-day exploitation window · FIRST.org · updated daily
VULNERABLE: UNKNOWN / CHECK VENDOR
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
4.7
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2024-2568 is a critical SQL injection vulnerability discovered in the heyewei JFinalCMS version 5.0.0. The flaw resides in the /admin/div_data/delete?divId=9 endpoint of the Custom Data Page component. An attacker can manipulate the divId parameter to inject arbitrary SQL commands, leading to unauthorized data access, modification, or deletion. The exploit has been publicly disclosed, increasing the risk of active exploitation. No official patch is currently available, making this a high-priority issue for any organization using JFinalCMS 5.0.0.

⚡ 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

CVSS Breakdown & Threat Level

  • CVSS Score: 4.7 (Medium)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
  • Attack Vector: Network (AV:N) – The vulnerability can be exploited remotely.
  • Attack Complexity: Low (AC:L) – No special conditions are required.
  • Privileges Required: None (PR:N) – No authentication needed.
  • User Interaction: None (UI:N) – No user action is required.
  • Scope: Unchanged (S:U) – The exploit does not affect other components.
  • Confidentiality Impact: Low (C:L) – Limited data exposure possible.
  • Integrity Impact: Low (I:L) – Limited data modification possible.
  • Availability Impact: None (A:N) – No denial of service.

Threat Level: Medium. The low EPSS score (0.0%) suggests limited active exploitation currently, but the public exploit disclosure and lack of patch elevate the risk for targeted attacks.

Deep Dive & Mechanics

The vulnerability is a classic SQL injection in the divId parameter of the /admin/div_data/delete endpoint. The application fails to sanitize or parameterize user input before constructing SQL queries. An attacker can inject SQL commands by appending malicious payloads to the divId parameter.

Example vulnerable request:

GET /admin/div_data/delete?divId=9' OR '1'='1' -- HTTP/1.1
Host: target.com

This would cause the application to execute a query like:

DELETE FROM custom_data WHERE id = 9' OR '1'='1' -- ;

Resulting in deletion of all rows in the custom_data table.

The attack is unauthenticated and requires no special privileges, making it easily exploitable by anyone with network access to the CMS.

Vulnerable vs. Patched Code

Vulnerable Code (JFinalCMS 5.0.0):

// Controller method
public void delete() {
    String divId = getPara("divId");
    // Direct concatenation into SQL
    String sql = "DELETE FROM custom_data WHERE id = " + divId;
    Db.update(sql);
}

Patched Code (Hypothetical fix):

// Controller method
public void delete() {
    Integer divId = getParaToInt("divId");
    // Parameterized query
    String sql = "DELETE FROM custom_data WHERE id = ?";
    Db.update(sql, divId);
}

The patched version uses parameterized queries, preventing SQL injection by separating SQL logic from user input.

Exploitation & Lab Setup

Red Team (Offensive)

Lab Setup:

  1. Deploy JFinalCMS 5.0.0 on a local server (e.g., using Docker or a VM).
  2. Ensure the /admin/div_data/delete endpoint is accessible.

Exploitation Steps:

  1. Basic Injection: Test with divId=9' OR '1'='1' -- to delete all records.
  2. Data Extraction: Use UNION-based injection to extract data:
    GET /admin/div_data/delete?divId=9 UNION SELECT username,password FROM users -- HTTP/1.1
    
  3. Blind Injection: Use time-based payloads if error messages are suppressed:
    GET /admin/div_data/delete?divId=9 AND SLEEP(5) -- HTTP/1.1
    

Automated Exploitation: Use sqlmap for automated exploitation:

sqlmap -u "http://target.com/admin/div_data/delete?divId=9" --batch --dbs

Blue Team (Defensive)

Detection:

  • Monitor for unusual SQL error messages in logs.
  • Alert on requests to /admin/div_data/delete with suspicious divId values (e.g., containing SQL keywords like OR, UNION, --).

Mitigation:

  • Immediately restrict access to the /admin/div_data/delete endpoint via firewall or web application firewall (WAF) rules.
  • Implement input validation to allow only numeric values for divId.
  • Apply a virtual patch using a WAF to block SQL injection patterns.

Indicators of Compromise (IOCs)

  • Network IOCs:

    • HTTP requests to /admin/div_data/delete with divId containing SQL keywords (e.g., OR, UNION, SELECT, SLEEP).
    • Unusual database error messages in HTTP responses (e.g., "You have an error in your SQL syntax").
  • File IOCs:

    • Unexpected entries in database logs indicating unauthorized queries.
    • Modified or deleted records in the custom_data table.
  • Behavioral IOCs:

    • Unusual database load or slow response times due to time-based injection attempts.
    • Multiple failed login attempts followed by exploitation attempts.

Detection Engineering

YARA Rule

rule CVE_2024_2568_SQLi {
    meta:
        description = "Detects SQL injection attempts targeting CVE-2024-2568 in JFinalCMS"
        author = "Valters IT"
        date = "2024-10-27"
        reference = "https://nvd.nist.gov/vuln/detail/CVE-2024-2568"
    strings:
        $sqli1 = "divId=" nocase
        $sqli2 = "OR" nocase
        $sqli3 = "UNION" nocase
        $sqli4 = "SELECT" nocase
        $sqli5 = "SLEEP" nocase
        $sqli6 = "--" nocase
    condition:
        all of ($sqli1, $sqli2) or all of ($sqli1, $sqli3) or all of ($sqli1, $sqli4) or all of ($sqli1, $sqli5) or all of ($sqli1, $sqli6)
}

Sigma Rule

title: CVE-2024-2568 SQL Injection Attempt
id: 12345678-1234-1234-1234-123456789012
status: experimental
description: Detects SQL injection attempts against JFinalCMS /admin/div_data/delete endpoint
author: Valters IT
date: 2024/10/27
references:
    - https://nvd.nist.gov/vuln/detail/CVE-2024-2568
logsource:
    category: webserver
    product: apache
    service: access_combined
detection:
    selection:
        cs-uri-query|contains:
            - "/admin/div_data/delete?divId="
        cs-uri-query|contains|all:
            - "OR"
            - "UNION"
            - "SELECT"
            - "SLEEP"
            - "--"
    condition: selection
falsepositives:
    - Legitimate use of these keywords in rare cases
level: high

Suricata Rule

alert http any any -> any any (msg:"CVE-2024-2568 SQL Injection Attempt"; flow:to_server,established; content:"/admin/div_data/delete?divId="; http_uri; pcre:"/(OR|UNION|SELECT|SLEEP|--)/Ri"; classtype:web-application-attack; sid:1000001; rev:1;)

Remediation & Mitigation

Immediate Actions:

  1. Isolate the CMS: If possible, take the JFinalCMS instance offline or restrict network access to trusted IPs only.
  2. Apply Virtual Patch: Use a WAF to block requests containing SQL injection patterns in the divId parameter.
  3. Input Validation: Implement server-side validation to ensure divId is an integer.

Long-Term Fix:

  • Upgrade to a patched version of JFinalCMS once available.
  • If no patch is released, consider migrating to a different CMS or manually fixing the code by using parameterized queries.

Monitoring:

  • Enable detailed logging for all requests to /admin/div_data/delete.
  • Set up alerts for any SQL injection patterns detected in logs.

Valters IT
DevSecOps & Cyber Threat Intelligence Expert

◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2024-2568/ · 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.