Skip to main content

SEMCMS CVE-2026-108813

| EUVDEUVD-2026-97289 LOW
SQL Injection (CWE-89)
2026-10-12 VulDB GHSA-72xg-5g4x-pqhq
2.1
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate with low-privilege account
  2. Delivery
    Send crafted request to SEMCMS_Download.php
  3. Exploit
    Inject SQL via manipulated parameter
  4. Execution
    Database executes attacker query
  5. Impact
    Exfiltrate or alter stored data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation targets the SEMCMS_Download.php endpoint specifically, where a user-controlled parameter is manipulated and passed unsanitized into a SQL query. Per the only available CVSS data (PR:L), a low-privileged authenticated session is required, which limits exposure to attackers who can reach and log into the application; however, this authentication requirement is taken from the vector alone and is not confirmed by a vendor advisory, so whether SEMCMS_Download.php is actually gated behind authentication should be verified. All versions of SEMCMS up to and including 5.0 are reportedly affected, and no patch is available because the vendor did not respond to the disclosure.

Impact

This is a SQL injection flaw (CWE-89) in SEMCMS's SEMCMS_Download.php, reachable over the network with low privileges per the sole CVSS signal provided (CVSS:4.0 AV:N/AC:L/AT:N/PR:L/UI:N, impacts VC:L/VI:L/VA:L). The vendor-assigned CVSS 4.0 base score of 2.1 is unusually low for an SQLi, driven by the Low confidentiality/integrity/availability ratings and the PR:L requirement - real-world SQLi often yields fuller database read/write, so the Low impact scoring may understate actual risk; verify the injection's reach before deprioritizing. POC availability is CONFIRMED (public exploit on GitHub, E:P in the vector), but there is NO CISA KEV listing and NO EPSS score in the input, so publicly available exploit code exists without evidence of active or widespread exploitation. The source is VulDB (a single CNA/aggregator), the product is niche, and the vendor was non-responsive with no patch, meaning exposed instances stay vulnerable. Net: a credible, real but modest-priority issue - exploit code lowers the bar, yet low deployment footprint, the PR:L authentication requirement, and absence of KEV/EPSS argue against emergency treatment. Note the conflict: a public exploit against an unpatched product normally raises urgency, while the vendor's own Low-impact CVSS pulls it down.

Exploit ScenarioDerived

An attacker with low-level authenticated access to a SEMCMS site sends a crafted request to SEMCMS_Download.php containing a malicious SQL payload in a manipulated parameter, which the application concatenates into a database query. Because a public proof-of-concept already exists (GitHub, ants01), the attacker can reuse it directly to extract or tamper with database contents. The CVSS vector indicates network reach and low attack complexity, so the request requires no special timing or local access.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 12, 2026

SQL injection in SEMCMS 5.0 and earlier lets an attacker manipulate a user-controlled parameter handled by SEMCMS_Download.php so that unsanitized input is passed into a backend SQL query, exposing and potentially modifying database contents. Per the CVSS vector (PR:L) a low-privileged authenticated session is required, which narrows exposure to actors who can reach and log into the application, although that authentication requirement is derived from the vector alone and has not been confirmed by a vendor advisory. Publicly available exploit code exists (referenced from a GitHub PoC repository), the CVSS 4.0 vector carries an Exploit Maturity of E:P, and the vendor was contacted early but did not respond; no vendor-released patch was identified at time of analysis.

RemediationAI

No vendor-released patch was identified at time of analysis - the vendor was contacted about the disclosure and did not respond, and no fixed SEMCMS version is published in any of the available references (https://vuldb.com/vuln/416590, https://vuldb.com/cve/CVE-2026-108813), so remediation must be compensating rather than version-based. The most direct control is to remove or disable SEMCMS_Download.php if the download feature is not required; the trade-off is loss of that functionality for legitimate users, but it eliminates the vulnerable code path entirely. If the script must stay live, place it behind an authentication and authorization check that only the intended audience can pass, and restrict the endpoint by IP allowlist or reverse-proxy ACL so only trusted networks reach it - this narrows exposure but does not fix the injection and breaks access for legitimate remote users. Add a WAF/reverse-proxy rule that rejects SQL metacharacters and boolean/UNION patterns on requests to SEMCMS_Download.php, accepting that signature-based filtering is bypassable and may generate false positives on legitimate filename parameters. Because the flaw lives in query construction, the durable fix is code-level: replace string concatenation with parameterized/prepared statements in SEMCMS_Download.php and validate the parameter against an expected type before use, which requires a locally maintained fork since no upstream patch is coming. Finally, minimize the blast radius by reducing the privileges of application database accounts and by limiting the number of low-privileged accounts that can authenticate, since the assessed vector assumes a low-privileged authenticated session is required; pair this with database query logging and alerting on anomalous SELECT/UNION traffic from the SEMCMS host so exploitation attempts are detectable even while unpatched.

Affected VersionsENISA

SEMCMS 5.0

Affected Packages

euvd semcms no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

SEMCMS is a PHP-based content management system, and CVE-2026-108813 is a textbook CWE-89 (Improper Neutralization of Special Elements used in an SQL Command) flaw in its download handling component, SEMCMS_Download.php. The root cause class is SQL injection: a request parameter is taken from the HTTP request and concatenated or interpolated into a SQL statement without parameterization or proper escaping, so an attacker who controls that parameter can alter the query's logic. Because the vector is network-reachable (AV:N/AC:L) and the exploit is described as public with an exploit-maturity rating of Proof-of-Concept (E:P), the practical difficulty of reproducing the issue is low; the primary gate is the PR:L privilege requirement noted in the CVSS 4.0 vector, meaning a low-privileged authenticated account is the assumed starting point in the only scoring signal available. Our independent assessment scores the flaw CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N - high confidentiality impact (bulk database read, including credential and configuration tables), low integrity impact (limited ability to alter data), and no availability impact - which is more aggressive on confidentiality than the coarse Low/Low/Low impact triad in the submitted CVSS 4.0 vector (score 2.1). The affected-product CPE is a placeholder (cpe:2.3:a:n/a:semcms:*:*:*:*:*:*:*:*) with no version bounds recorded, and the vendor/product fields are unassigned, which is typical for small-vendor CVE entries that lack a CNA advisory and should be treated as an indicator of thin vendor-side documentation rather than a safe version.

Know when Semcms gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 2.1 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
vuln.today AI 7.1 HIGH

Network-reachable, low-complexity SQLi with PR:L per the supplied vector; SQL injection typically permits full database read (C:H) with limited write (I:L) and no availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

3
Severity Changed
Oct 12, 2026 - 08:22 NVD
MEDIUM LOW
CVSS changed
Oct 12, 2026 - 08:22 NVD
5.3 (MEDIUM) 2.1 (LOW)
CVE Published
Oct 12, 2026 - 07:45 cve.org
LOW 2.1

DescriptionCVE.org

A vulnerability was detected in SEMCMS up to 5.0. This affects an unknown function of the file SEMCMS_Download.php. Performing a manipulation results in sql injection. It is possible to initiate the attack remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Threat Intelligence Overview

EPSS Score
0.2%
Top 92% exploitable
Prevalence
Low
niche foreign-trade website CMS, limited enterprise footprint
Exploit
POC
Public exploit code exists
Social Media
1
Sightings
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity LOW
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
Poc
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Low

Priority Score

30
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +10
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

More in Semcms

View all
CVE-2025-25686 CRITICAL POC
9.8 Mar 27

semcms <=5.0 is vulnerable to SQL Injection in SEMCMS_Fuction.php. Rated critical severity (CVSS 9.8), this vulnerabilit

CVE-2024-46103 CRITICAL POC
9.8 Sep 20

SEMCMS 4.8 is vulnerable to SQL Injection via SEMCMS_Main.php. Rated critical severity (CVSS 9.8), this vulnerability is

CVE-2024-31012 CRITICAL POC
9.8 Apr 03

An issue was discovered in SEMCMS v.4.8, allows remote attackers to execute arbitrary code, escalate privileges, and obt

CVE-2024-25422 CRITICAL POC
9.8 Feb 28

SQL Injection vulnerability in SEMCMS v.4.8 allows a remote attacker to execute arbitrary code and obtain sensitive info

CVE-2023-50563 CRITICAL POC
9.8 Dec 14

Semcms v4.8 was discovered to contain a SQL injection vulnerability via the AID parameter at SEMCMS_Function.php. Rated

CVE-2023-31707 CRITICAL POC
9.8 May 19

SEMCMS 1.5 is vulnerable to SQL Injection via Ant_Rponse.php. Rated critical severity (CVSS 9.8), this vulnerability is

CVE-2018-18742 HIGH POC
8.8 Oct 29

A CSRF issue was discovered in SEMCMS 3.4 via the admin/SEMCMS_User.php?Class=add&CF=user URI. Rated high severity (CVSS

CVE-2023-48864 HIGH POC
7.5 Jan 10

SEMCMS v4.8 was discovered to contain a SQL injection vulnerability via the languageID parameter in /web_inc.php. Rated

CVE-2024-36800 HIGH POC
7.5 Jun 04

A SQL injection vulnerability in SEMCMS v.4.8, allows a remote attacker to obtain sensitive information via the ID param

CVE-2024-31010 HIGH POC
7.5 Apr 03

SQL injection vulnerability in SEMCMS v.4.8, allows a remote attacker to obtain sensitive information via the ID paramet

CVE-2023-48863 HIGH POC
7.5 Dec 04

SEMCMS 3.9 is vulnerable to SQL Injection. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, n

CVE-2024-28405 HIGH POC
7.2 Mar 29

SEMCMS 4.8 is vulnerable to Incorrect Access Control. Rated high severity (CVSS 7.2), this vulnerability is remotely exp

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy