VulnerabilityPublished 21 Dec 2025Updated 24 Feb 2026

CVE-2025-15003: SeaCMS · SQL Injection

Affects SeaCMSSource CVE Database V5

Public exploit available · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
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

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
SeaCMS	Affected 13.0 – 13.3 4 affected builds	Fixed in–

AI-suggested

To mitigate CVE-2025-15003, organizations should first verify if they are running affected SeaCMS versions (13.0 to 13.3) and prioritize upgrading to a patched version once available. In the absence of official patches, immediate steps include implementing strict input validation and sanitization on the e_id parameter to prevent injection of malicious SQL code. Employing parameterized queries or prepared statements in the admin_video.php file can effectively neutralize injection attempts. Restrict access to the admin interface by IP whitelisting, VPNs, or multi-factor authentication to reduce exposure to unauthorized users. Regularly audit user privileges to ensure only necessary users have high-level access. Monitoring database logs and web application logs for suspicious queries or unusual activity can help detect exploitation attempts early. Additionally, consider deploying web application firewalls (WAFs) with custom rules to block SQL injection payloads targeting the vulnerable parameter. Educate administrators about the risks and signs of SQL injection attacks to improve incident response readiness.

Description

A vulnerability was found in SeaCMS up to 13.3. The impacted element is an unknown function of the file admin_video.php. Performing a manipulation of the argument e_id results in sql injection. The attack is possible to be carried out remotely. The exploit has been made public and could be used.

Impact

The SQL injection vulnerability in SeaCMS can have significant impacts on affected organizations. Successful exploitation could allow attackers to execute arbitrary SQL commands on the backend database, leading to unauthorized data disclosure, data modification, or deletion. This compromises the confidentiality and integrity of the stored information. Additionally, attackers might disrupt service availability by corrupting database contents or causing application errors. Since the vulnerability requires high privileges, the attack surface is somewhat limited to authenticated users with elevated rights, but insider threats or compromised credentials could facilitate exploitation. Organizations relying on SeaCMS for critical content management may face reputational damage, regulatory compliance issues, and operational disruptions if this vulnerability is exploited. The public availability of exploit code increases the likelihood of automated attacks or exploitation by less skilled adversaries, raising the urgency for mitigation.

Summary

CVE-2025-15003 is a SQL injection vulnerability identified in SeaCMS, a content management system, affecting versions 13.0 through 13.3. The vulnerability resides in an unspecified function within the admin_video.php file, where the e_id parameter is improperly sanitized, allowing an attacker to inject malicious SQL code. This injection flaw can be exploited remotely without user interaction but requires the attacker to have high privileges, indicating that some form of authentication or elevated access is necessary before exploitation. The vulnerability can lead to unauthorized database queries, potentially exposing or altering sensitive data, or disrupting service availability. The CVSS 4.0 base score is 5.1, reflecting medium severity, with network attack vector, low complexity, no user interaction, and partial impacts on confidentiality, integrity, and availability. Although no active exploitation in the wild has been reported, the public availability of exploit code increases the risk of future attacks. SeaCMS is used globally, primarily by small to medium enterprises for website content management, making this vulnerability relevant for organizations relying on this CMS platform. The lack of official patches or mitigation guidance in the provided data suggests that users must implement defensive coding practices or restrict access to vulnerable components until updates are available.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Feb 2026, 23:10 UTC

Technical details

References

Community reviews

Related threats