dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-28904

CRITICAL · 9.3 CVSS v3.1 Published 2025-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Shamalli Web Directory Free web-directory-free allows Blind SQL Injection.This issue affects Web Directory Free: from n/a through <= 1.7.6.

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

A Blind SQL Injection vulnerability exists in Shamalli Web Directory Free (versions <= 1.7.6) where user-supplied input is not properly sanitized before being used in SQL queries. An attacker can inject malicious SQL statements through unprotected input parameters, potentially extracting sensitive data from the database or compromising the entire application.

MitigationUpgrade to a patched version if available, or remediate by implementing parameterized queries/prepared statements for all database interactions, applying proper input validation, and employing least-privilege database accounts.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/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 Shamalli Web Directory Free is installed
    Locate the application files on the web server. Look for directories containing 'shamalli' or 'web directory' in the file path, or check the application name displayed in the web interface header/footer.
    Affected if The application is Shamalli Web Directory Free and the version is unknown or <= 1.7.6
  2. Determine the installed version
    Check for a version file (often version.php, about.php, or similar) within the application root directory, or look for a version string in the admin panel 'About' or 'System Info' section.
    Affected if The version cannot be determined or is found to be 1.7.6 or lower
  3. Identify accessible user input parameters
    Review the application's forms and URL parameters that accept user input, such as search fields, login forms, contact forms, or any parameter passed via GET/POST requests.
    Affected if The application accepts user input through web forms or URL parameters without evident input validation
  4. Verify if SQL queries use prepared statements
    Examine the application's source code files (especially PHP files in the includes or functions directories) for SQL query patterns. Look for direct string concatenation of user input into SQL queries versus parameterized queries using PDO or mysqli prepared statements.
    Affected if SQL queries are constructed by directly concatenating user input into query strings without using prepared statements or parameterized queries
  5. Test for SQL injection vulnerability (if authorized)
    Using a web vulnerability scanner or manual testing with SQL injection payloads (such as adding a single quote ' or boolean-based payloads like ' OR 1=1-- to input parameters), observe if the application returns database errors or behaves differently based on injected content.
    Affected if The application exhibits unexpected behavior, displays database errors, or returns different content when SQL injection payloads are submitted
  6. Check database account privileges
    Review the database configuration file (often config.php, db.php, or similar) to identify the database user credentials, then verify the privileges granted to that database account.
    Affected if The application connects to the database using an account with elevated privileges (such as root or admin) rather than a least-privilege account

If Shamalli Web Directory Free version 1.7.6 or lower is in use and SQL queries do not utilize prepared statements, the application is likely vulnerable to CVE-2025-28904.

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

Upgrade to a patched version if available, or remediate by implementing parameterized queries/prepared statements for all database interactions, applying proper input validation, and employing least-privilege database accounts.

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-28904 — 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-28904 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