dbcve.org
LedgersmbWeb browser

CVE-2007-1437

HIGH · 9.0 CVSS v2.0 Published 2007-03-13
Fix available
A fix is available. Upgrade to after 2.6.24 or later.
See remediation →
96/100
Remediation priority · Urgent
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
Unspecified vulnerability in LedgerSMB before 1.1.5 and SQL-Ledger before 2.6.25 allows remote attackers to overwrite files and possibly bypass authentication, and remote authenticated users to execute unauthorized code, by calling a custom error function that returns from execution.

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

Vulnerability in LedgerSMB before 1.1.5 and SQL-Ledger before 2.6.25 allows remote attackers to overwrite files and possibly bypass authentication via a custom error function that returns from execution. Authenticated remote users can also execute unauthorized code.

MitigationUpgrade to LedgerSMB 1.1.5 or SQL-Ledger 2.6.25 or later to remediate this vulnerability.

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
LedgersmbWeb browser
Affected:= 1.0.0= 1.1.0= 1.1.1
Sql LedgerWeb browser
Affected:<= 2.6.24

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

AV:N/AC:L/Au:S/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 version
    Locate the version file or check the main Perl module for the version string. Common locations include the setup.pl script, the bin/ directory, or the default.pm file.
    Affected if The installed version is 1.0.0, 1.1.0, or 1.1.1 (exactly as listed in affected versions)
  2. Identify the installed SQL-Ledger version
    Locate the version file or check the main Perl module for the version string, typically in the root or bin directory of the SQL-Ledger installation.
    Affected if The installed version is 2.6.24 or lower (versions <= 2.6.24)
  3. Check if the application is network accessible
    Verify whether the web interface is exposed to remote network connections or only bound to localhost/internal interfaces.
    Affected if The application is accessible from untrusted network locations (required for remote attacker exploitation)
  4. Examine custom error handling configuration
    Review the application's error handling code or configuration files for custom error functions that return from execution, as mentioned in the vulnerability description.
    Affected if A custom error function is implemented and returns from execution, allowing file overwrite or authentication bypass

You are affected if you are running LedgerSMB versions 1.0.0, 1.1.0, or 1.1.1, or SQL-Ledger version 2.6.24 or earlier, with the web interface network-accessible and custom error handling enabled.

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 2.6.24
Interim mitigation

Upgrade to LedgerSMB 1.1.5 or SQL-Ledger 2.6.25 or later to remediate this vulnerability.

Recommended fix High confidence

LedgerSMB 1.1.5+ or SQL-Ledger 2.6.25+

  1. 1. Back up the existing LedgerSMB/SQL-Ledger database and configuration files
  2. 2. Download the fixed version: LedgerSMB 1.1.5 or later, or SQL-Ledger 2.6.25 or later
  3. 3. Replace the existing installation files with the new version
  4. 4. Review and restore any custom configuration changes from the backup
  5. 5. Restart the web server/application service
  6. 6. Verify that the custom error function vulnerability is no longer present by testing file operations and authentication
Caveat Upgrading from such old versions (1.0.0-1.1.1 / <=2.6.24) may have compatibility impacts with older customizations, templates, or database schemas; thoroughly test in a staging environment before production deployment

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

Fix this in Ledgersmb Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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