dbcve.org
DedebizApplication

CVE-2025-12860

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 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.

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 · high confidence

SQL injection vulnerability in DedeBIZ up to 6.3.2 in the /admin/freelist_main.php file allows remote authenticated attackers to inject malicious SQL queries through the unsanitized orderby parameter.

MitigationUpgrade to a patched version of DedeBIZ (version > 6.3.2). If upgrade is not immediately possible, implement strict input validation on the orderby parameter or use parameterized queries to prevent SQL injection.

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 is installed
    Locate DedeBIZ by checking for the presence of typical DedeBIZ directories (e.g., /admin/, /include/, /uploads/) or the index.php file containing 'DedeBIZ' or 'Dede' branding in the web root.
    Affected if The web application is running DedeBIZ.
  2. Check DedeBIZ version
    Locate the version indicator. Common locations include a version.php file, the admin footer, or a /data/admin/ver.txt file. Compare the installed version number to 6.3.2.
    Affected if The installed version is 6.3.2 or lower.
  3. Verify vulnerable file exists
    Check for the presence of the file /admin/freelist_main.php in the web root directory.
    Affected if The file /admin/freelist_main.php exists on the server.
  4. Check admin access exposure
    Determine if the /admin/ directory is publicly accessible. Attempt to access the admin login page or check web server configuration for admin path access rules.
    Affected if The admin interface is accessible from the network without additional access restrictions.
  5. Inspect orderby parameter handling
    Examine the source code of /admin/freelist_main.php. Search for the 'orderby' parameter usage and verify whether it is directly concatenated into SQL queries without sanitization or use of parameterized queries.
    Affected if The orderby parameter is used in SQL queries without prepared statements, binding, or input validation.

The environment is affected if DedeBIZ version 6.3.2 or lower is installed, the file /admin/freelist_main.php exists, the admin panel is accessible, and the orderby parameter in that file lacks SQL injection protection.

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 a patched version of DedeBIZ (version > 6.3.2). If upgrade is not immediately possible, implement strict input validation on the orderby parameter or use parameterized queries to prevent SQL injection.

Recommended fix Moderate confidence

DedeBIZ 6.3.3 or later (check GitHub for latest stable release)

  1. 1. Check the official DedeBIZ GitHub repository (github.com/dedebiz/DedeBIZ) for the latest release version beyond 6.3.2
  2. 2. If a newer stable version (e.g., 6.3.3 or later) is available, upgrade to that version to receive the SQL injection fix
  3. 3. After upgrading, verify the /admin/freelist_main.php file has been patched or updated
  4. 4. As a temporary mitigation before upgrading, disable or restrict access to the /admin/freelist_main.php file using web server access controls (e.g., .htaccess or IP allowlisting)
  5. 5. If the admin panel is not required externally, ensure it is only accessible from trusted IP addresses
  6. 6. After applying the fix, test the freelist_main.php functionality to ensure the orderby parameter is properly sanitized
Caveat Minor - verify custom templates or workflows using the freelist functionality still work after upgrade

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

Fix this in Dedebiz Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,950
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12860 — 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-12860 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