dbcve.org
DedebizApplication

CVE-2025-12859

HIGH · 7.2 CVSS v3.1 Published 2025-11-07
Fix available
A fix is available. Upgrade to after 6.3.2 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability has been found in DedeBIZ up to 6.3.2. This impacts an unknown function of the file /admin/templets_one_edit.php. The manipulation of the argument ids leads to sql injection. Remote exploitation of the attack is possible. The exploit has been disclosed to the public and may be used.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

SQL injection vulnerability in DedeBIZ up to version 6.3.2 in the file /admin/templets_one_edit.php. The 'ids' parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL code.

MitigationUpgrade to DedeBIZ version 6.3.3 or later, or apply parameterized queries/input validation to the 'ids' parameter in templets_one_edit.php.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DedebizApplication
Affected:<= 6.3.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm DedeBIZ installation
    Look for DedeBIZ in your web directory. Check for common indicators like /admin/ folder, or look for DedeBIZ-specific files. Check version file if exists (commonly VERSION or version.php in root or data folder)
    Affected if DedeBIZ is installed and version is 6.3.2 or lower
  2. Verify vulnerable file exists
    Check if the file /admin/templets_one_edit.php exists in your DedeBIZ installation directory
    Affected if The file templets_one_edit.php exists in the /admin/ directory
  3. Check the exposed parameter handling
    Examine the templets_one_edit.php file and look for how the 'ids' parameter is handled. Look for direct usage of $_GET['ids'] or $_POST['ids'] in SQL queries without sanitization or parameterization
    Affected if The 'ids' parameter is used directly in SQL queries without prepared statements or proper escaping
  4. Confirm version is within affected range
    Compare your installed DedeBIZ version against the affected range: versions 6.3.2 and below. If you cannot determine the exact version but have confirmed DedeBIZ is present, treat it as potentially affected
    Affected if Installed version is 6.3.2 or lower, or version cannot be determined but DedeBIZ is present

Your environment is affected if DedeBIZ is installed with version 6.3.2 or lower and the file /admin/templets_one_edit.php exists with the vulnerable 'ids' parameter handling.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 6.3.2
Interim mitigation

Upgrade to DedeBIZ version 6.3.3 or later, or apply parameterized queries/input validation to the 'ids' parameter in templets_one_edit.php.

Recommended fix Moderate confidence

DedeBIZ 6.3.3 or later (any version newer than 6.3.2)

  1. 1. Backup your current DedeBIZ installation and database before proceeding with any upgrade.
  2. 2. Download the latest stable version of DedeBIZ from the official repository (github.com/dedebiz/DedeBIZ).
  3. 3. Replace the existing DedeBIZ files with the new version, preserving your configuration files and customizations.
  4. 4. Run any database migration scripts included in the upgrade package.
  5. 5. Verify the admin/templets_one_edit.php file has been updated and no longer contains the vulnerable code.
  6. 6. Test the templets_one_edit.php functionality to ensure the fix works correctly.
  7. 7. Monitor logs for any SQL injection attempts to confirm the vulnerability is no longer exploitable.
Caveat Minor breaking changes possible; review release notes before upgrading and test in staging environment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dedebiz Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12859 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12859 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data