dbcve.org
InjectionWeakness · CWE-74

CVE-2025-1544

MEDIUM · 6.3 CVSS v3.1 Published 2025-02-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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, which was classified as critical, was found in dingfanzu CMS up to 20250210. Affected is an unknown function of the file /ajax/loadShopInfo.php. The manipulation of the argument shopId leads to sql injection. It is possible to launch the attack 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.

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 dingfanzu CMS /ajax/loadShopInfo.php where the shopId parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries. The vulnerability is exploitable remotely and a proof-of-concept exploit has been publicly disclosed.

MitigationImplement prepared statements/parameterized queries for the shopId parameter in loadShopInfo.php, or apply input validation and escaping if parameterized queries are not feasible. Consider input sanitization as an interim measure until a vendor patch is available.

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

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Identify if dingfanzu CMS is installed
    Search the web root directory for files or directories containing 'dingfanzu' or check common CMS installation paths. Look for loadShopInfo.php in the /ajax/ directory.
    Affected if dingfanzu CMS is present and the /ajax/loadShopInfo.php file exists
  2. Locate the vulnerable file
    Navigate to the web root and locate /ajax/loadShopInfo.php. This file should exist in the affected CMS installation.
    Affected if The file /ajax/loadShopInfo.php is found in the application directory
  3. Check shopId parameter handling
    Open loadShopInfo.php and inspect the code around the shopId parameter. Look for direct use of $_GET['shopId'] or $_POST['shopId'] in SQL queries without prepared statements, parameter binding, or escaping functions.
    Affected if The shopId parameter is used directly in SQL queries without parameterized queries, escaping, or input validation
  4. Check database query implementation
    Examine all SQL queries in loadShopInfo.php that incorporate the shopId variable. Verify if the query string is constructed by concatenating or interpolating the parameter directly.
    Affected if SQL queries concatenate the shopId parameter directly into the query string
  5. Verify application version
    Check for version files, changelogs, or admin panels within the dingfanzu CMS installation that might reveal the installed version number.
    Affected if The installed version falls within any known affected version range (compare to vendor advisories if available)
  6. Check web server logs for exploitation attempts
    Review access logs for requests to /ajax/loadShopInfo.php containing SQL injection payloads in the shopId parameter.
    Affected if Malicious requests with SQL injection payloads in shopId parameter are found in logs

A user is affected if dingfanzu CMS is installed with the /ajax/loadShopInfo.php file present and the shopId parameter is used in SQL queries without proper sanitization or prepared statements.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement prepared statements/parameterized queries for the shopId parameter in loadShopInfo.php, or apply input validation and escaping if parameterized queries are not feasible. Consider input sanitization as an interim measure until a vendor patch is available.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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