CVE-2025-12860VulnerabilityPublished 7 Nov 2025Updated 24 Feb 2026

CVE-2025-12860: DedeBIZ · SQL Injection

Affects DedeBIZSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 06:26 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 25% 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 7 Nov 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
GitHubdedebiz/DedeBIZ`pkg:github/dedebiz/DedeBIZ`Other threats	Affected =6.3.0 =6.3.1 =6.3.2	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. Restrict access to the /admin/freelist_main.php interface by implementing network-level controls such as VPNs, IP whitelisting, or firewall rules to limit exposure to trusted administrators only. 2. Apply strict input validation and sanitization on the 'orderby' parameter, ensuring only expected values or safe characters are accepted. 3. Employ parameterized queries or prepared statements in the application code to prevent SQL injection. 4. Monitor logs for unusual or suspicious SQL queries targeting the 'orderby' parameter or admin endpoints. 5. Regularly audit user privileges to ensure only necessary users have high-level access to the admin panel. 6. Stay updated with vendor advisories and apply official patches or updates as soon as they become available. 7. Consider deploying Web Application Firewalls (WAFs) with rules to detect and block SQL injection attempts targeting this vulnerability. 8. Conduct security assessments and penetration testing focusing on admin interfaces to identify and remediate similar injection flaws.

Description

A vulnerability was found in DedeBIZ up to 6.3.2. Affected is an unknown function of the file /admin/freelist_main.php. The manipulation of the argument orderby results in sql injection. The attack can be executed remotely. The exploit has been made public and could be used.

Impact

The SQL injection vulnerability in DedeBIZ can lead to unauthorized access to sensitive database information, data corruption, or deletion, potentially disrupting business operations. Attackers with high privileges could leverage this flaw to escalate their access, extract confidential data, or manipulate application behavior. For organizations relying on DedeBIZ for content management, this could result in data breaches, loss of customer trust, regulatory penalties, and operational downtime. Since the vulnerability is remotely exploitable without user interaction, it poses a significant risk if administrative interfaces are exposed to untrusted networks. The medium severity rating indicates a moderate but tangible threat, especially in environments where administrative access controls are weak or compromised. The public availability of exploit code increases the likelihood of opportunistic attacks, emphasizing the need for prompt remediation.

Summary

CVE-2025-12860 is a SQL injection vulnerability identified in the DedeBIZ content management system, specifically in versions 6.3.0 through 6.3.2. The vulnerability resides in the /admin/freelist_main.php script, where the 'orderby' parameter is improperly sanitized, allowing an attacker to inject arbitrary SQL commands. This injection flaw can be exploited remotely without user interaction, but requires the attacker to have high privileges, likely meaning authenticated access to the admin panel or elevated user rights. The vulnerability impacts the confidentiality, integrity, and availability of the underlying database by enabling unauthorized data access, modification, or deletion. The CVSS 4.0 score of 5.1 reflects a medium severity, considering the ease of exploitation (low complexity), no user interaction, but the prerequisite of high privileges. Although no known exploits are currently active in the wild, the public disclosure of exploit code increases the risk of exploitation. The lack of vendor patches at the time of publication necessitates immediate mitigation steps by administrators. This vulnerability highlights the importance of proper input validation and parameterized queries in web applications to prevent injection attacks.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Feb 2026, 22:17 UTC

Technical details

References

Community reviews

Related threats