CVE-2025-6100VulnerabilityPublished 16 Jun 2025

CVE-2025-6100: realguoshuai open-video-cms · SQL Injection

Affects realguoshuai open-video-cmsSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.3Medium

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

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

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

Base metrics

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

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: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
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 16 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

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 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
GitHubrealguoshuai/open-video-cms`pkg:github/realguoshuai/open-video-cms`Other threats	Affected =1.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate mitigation should include implementing web application firewall (WAF) rules to detect and block suspicious SQL injection payloads targeting the 'sort' parameter on the /v1/video/list endpoint. 2. Conduct a thorough code review and input validation enhancement for all parameters, especially 'sort', to enforce strict type checking and whitelist acceptable values. 3. Employ parameterized queries or prepared statements in the database interaction layer to eliminate direct concatenation of user input into SQL commands. 4. Restrict database user privileges associated with the CMS to the minimum necessary, preventing unauthorized data modification or extraction even if injection occurs. 5. Monitor application logs for anomalous query patterns or repeated failed attempts indicative of exploitation attempts. 6. If feasible, isolate the CMS environment from critical internal networks to limit lateral movement in case of compromise. 7. Engage with the vendor or community to encourage patch development or consider migrating to alternative CMS solutions with active security maintenance. 8. Educate development and security teams about secure coding practices and the risks of SQL injection to prevent similar vulnerabilities in future deployments.

Description

A vulnerability was found in realguoshuai open-video-cms 1.0. It has been rated as critical. This issue affects some unknown processing of the file /v1/video/list. The manipulation of the argument sort leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations using open-video-cms 1.0, this vulnerability poses a tangible risk to the confidentiality and integrity of video content metadata and potentially user data stored within the CMS database. Exploitation could lead to unauthorized data disclosure, data tampering, or denial of service conditions affecting video content delivery platforms. Organizations operating video streaming services, media hosting, or educational platforms relying on this CMS may face reputational damage, regulatory compliance issues (e.g., GDPR breaches if personal data is exposed), and operational disruptions. Given the lack of vendor response and patch availability, the window for exploitation remains open, increasing the urgency for mitigation. The medium CVSS score suggests that while the vulnerability is exploitable remotely and easily, the overall damage may be contained if database permissions are properly restricted. However, in scenarios where the CMS is integrated with other critical systems or contains sensitive data, the impact could escalate. Additionally, public disclosure of the exploit details increases the likelihood of opportunistic attacks targeting European organizations.

Summary

CVE-2025-6100 is a SQL Injection vulnerability identified in version 1.0 of the open-source content management system (CMS) 'open-video-cms' developed by realguoshuai. The vulnerability resides in the processing of the /v1/video/list endpoint, specifically in the handling of the 'sort' parameter. Improper sanitization or validation of this parameter allows an attacker to inject malicious SQL code, potentially manipulating database queries executed by the application. This flaw can be exploited remotely without requiring user interaction or authentication, increasing the attack surface significantly. Although the vendor was notified early, no response or patch has been provided, and the exploit details have been publicly disclosed, raising the risk of exploitation. The CVSS 4.0 base score is 5.3 (medium severity), reflecting factors such as network attack vector, low attack complexity, no privileges or user interaction required, but limited impact on confidentiality, integrity, and availability. The vulnerability could allow attackers to extract sensitive data, modify database contents, or disrupt service depending on the underlying database permissions and application logic. However, the impact is rated as limited due to the partial scope of the injection and the absence of known exploits in the wild at the time of publication.

References

Community reviews

Loading reviews…