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

CVE-2025-12861: DedeBIZ · SQL Injection

Affects DedeBIZSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 08:30 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 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 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
GitHubzzctd/DedeBIZ`pkg:github/zzctd/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

To mitigate CVE-2025-12861, organizations should immediately restrict access to the /admin/spec_add.php endpoint to trusted administrators only, ideally through network segmentation or VPN access. Implement strict input validation and sanitization for the flags[] parameter to prevent SQL injection, using parameterized queries or prepared statements if source code modification is possible. Monitor database logs and web application logs for unusual queries or access patterns indicative of injection attempts. Employ web application firewalls (WAFs) with custom rules to detect and block SQL injection payloads targeting this parameter. Conduct thorough privilege audits to ensure users have the minimum necessary access, reducing the risk of exploitation by insiders or compromised accounts. Stay alert for official patches or updates from DedeBIZ developers and apply them promptly once available. Additionally, perform regular security assessments and penetration tests focusing on administrative interfaces to identify similar vulnerabilities proactively.

Description

A vulnerability was determined in DedeBIZ up to 6.3.2. Affected by this vulnerability is an unknown functionality of the file /admin/spec_add.php. This manipulation of the argument flags[] causes sql injection. The attack is possible to be carried out remotely. The exploit has been publicly disclosed and may be utilized.

Impact

The potential impact of CVE-2025-12861 includes unauthorized access to sensitive database information, data manipulation, and possible disruption of application functionality. Since exploitation requires high privileges, the threat is primarily to insiders or attackers who have already compromised lower-level credentials. However, if exploited, attackers could escalate privileges or extract confidential data, impacting the confidentiality and integrity of organizational data. The availability impact is limited but could occur if injected SQL commands disrupt database operations. Organizations relying on DedeBIZ for critical business functions or hosting sensitive data face risks of data breaches, compliance violations, and reputational damage. The medium severity rating reflects the balance between the required privilege level and the potential damage. The public disclosure without available patches increases the urgency for mitigation to prevent exploitation attempts, especially in environments with weak internal access controls.

Summary

CVE-2025-12861 is a SQL injection vulnerability identified in the DedeBIZ content management system, affecting versions 6.3.0 through 6.3.2. The vulnerability exists in the /admin/spec_add.php script, where the flags[] parameter is improperly sanitized, allowing attackers to inject malicious SQL code. This flaw can be exploited remotely without user interaction but requires the attacker to have high privileges (PR:H), indicating that some form of authentication or elevated access is necessary before exploitation. The CVSS 4.0 vector indicates network attack vector (AV:N), low complexity (AC:L), no user interaction (UI:N), and partial impacts on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). The vulnerability does not affect system confidentiality, integrity, or availability completely but can lead to unauthorized data access or modification. Although no known exploits are currently active in the wild, the public disclosure increases the risk of exploitation. The lack of patches or official fixes at the time of disclosure necessitates immediate mitigation efforts by administrators. The vulnerability highlights the importance of secure input validation and access control in administrative modules of web applications.

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