dbcve.org
Sql LedgerWeb browser · Dws Systems Inc.

CVE-2007-5372

HIGH · 10.0 CVSS v2.0 Published 2007-10-11
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
Multiple SQL injection vulnerabilities in (a) LedgerSMB 1.0.0 through 1.2.7 and (b) DWS Systems SQL-Ledger 2.x allow remote attackers to execute arbitrary SQL commands via (1) the invoice quantity field or (2) the sort field.

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

Multiple SQL injection vulnerabilities in LedgerSMB 1.0.0-1.2.7 and SQL-Ledger 2.x allow remote attackers to execute arbitrary SQL commands via the invoice quantity field and sort field parameters. These unsanitized user inputs are directly incorporated into SQL queries, enabling attackers to manipulate query logic and access, modify, or delete database contents.

MitigationImplement parameterized queries (prepared statements) for all database operations, particularly those handling the invoice quantity and sort parameters. Additionally, apply strict input validation and output encoding. If patches are available from the vendor, apply them immediately.

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
Sql LedgerWeb browser
Affected:= 2.2.0= 2.2.1= 2.2.2= 2.2.3= 2.2.4= 2.2.5= 2.2.6= 2.2.7= 2.4.0= 2.4.1= 2.4.2= 2.4.3
LedgersmbWeb browser
Affected:= 1.0.0= 1.1.0= 1.1.1= 1.1.5= 1.1.8= 1.2.0= 1.2.1= 1.2.2= 1.2.3= 1.2.4= 1.2.5= 1.2.6

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 the installed LedgerSMB or SQL-Ledger version
    Locate the application version by checking the software's about page, version file, or by querying the database if the version is stored there. Common locations include a version.pm file, the login screen footer, or the database itself.
    Affected if The installed version matches 1.0.0 through 1.2.7 for LedgerSMB, or 2.2.0 through 2.4.3 for SQL-Ledger as listed in the affected versions.
  2. Determine if the invoice module is accessible
    Check whether the invoice processing functionality is enabled and accessible to users. This typically involves verifying user roles and permissions within the application.
    Affected if Users with access to invoice creation, editing, or listing functions exist in the system.
  3. Locate the invoice quantity and sort parameter handlers
    Inspect the application source code, particularly the invoice handling scripts and any code that processes the quantity and sort GET/POST parameters.
    Affected if Code exists that directly incorporates the 'quantity' or 'sort' parameter values into SQL queries without using parameterized queries or input sanitization.
  4. Verify database query construction for the vulnerable parameters
    Search the codebase for SQL query strings that concatenate or interpolate the 'quantity' or 'sort' parameters directly into the WHERE or ORDER BY clauses.
    Affected if The invoice quantity field or sort field parameters are found being concatenated directly into SQL queries without prepared statements or escaping.
  5. Confirm the application processes user-supplied sort input
    Test or review code that handles the sort parameter in list views, particularly invoice lists, to see if user-provided values reach the database query.
    Affected if The sort parameter from user input is passed directly to the database without validation.

You are affected if you run any LedgerSMB version 1.0.0-1.2.7 or SQL-Ledger version 2.2.0-2.4.3 and the application processes invoice-related quantity or sort parameters without parameterized queries.

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 parameterized queries (prepared statements) for all database operations, particularly those handling the invoice quantity and sort parameters. Additionally, apply strict input validation and output encoding. If patches are available from the vendor, apply them immediately.

Fix this in Sql Ledger Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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