CVE-2007-0667
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 · uneditedThe redirect function in Form.pm for (1) LedgerSMB before 1.1.5 and (2) SQL-Ledger allows remote authenticated users to execute arbitrary code via redirects, related to callbacks, a different issue than CVE-2006-5872.
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 confidenceThe redirect function in Form.pm for LedgerSMB before 1.1.5 and SQL-Ledger contains a vulnerability allowing remote authenticated users to execute arbitrary code through malicious redirects via the callback mechanism. The vulnerability stems from insufficient validation of redirect targets, enabling attackers to inject and execute arbitrary code.
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<= 1.1.1= 2.4.7= 2.6.17= 2.6.18= 2.6.19= 2.6.21= 2.6.25CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/C:P/I:P/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Identify LedgerSMB or SQL-Ledger installation versionCheck the version file in the installation directory (often in a VERSION, ChangeLog, or ledgersmb.conf file). Alternatively, check the main Perl module files for version strings or the application's login page for version disclosure.Affected if The installed version is LedgerSMB <= 1.1.1 or SQL-Ledger = 2.4.7, 2.6.17, 2.6.18, 2.6.19, 2.6.21, or 2.6.25
-
Locate and examine Form.pmFind the Form.pm file in the Perl library path or application directory (typically in the lib/ or bin/ folder). Check the file modification date and look for any version comments at the top of the file.Affected if Form.pm exists and is from an unpatched version (before the 1.1.5 release), or if the file has not been updated since February 2007 when the patch was released.
-
Verify if the web interface is accessibleConfirm that the application web interface (typically running on Apache with mod_perl or as a CGI) is accessible. Check the web server configuration for LedgerSMB/SQL-Ledger aliases or virtual hosts.Affected if The web interface is exposed and the application is reachable over the network, making remote exploitation possible.
-
Check if user authentication is enabledExamine the application configuration to verify whether user authentication is required for accessing the redirect/callback functionality. Review the login mechanism and session management settings.Affected if User authentication is configured but the redirect/callback parameters are not being strictly validated, allowing authenticated users to inject malicious redirect targets.
You are affected if your installed version is LedgerSMB <= 1.1.1 or SQL-Ledger one of the listed vulnerable versions AND the web interface with user authentication is active, since the vulnerability exploits the redirect function in Form.pm through the callback mechanism.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to LedgerSMB 1.1.5 or later which contains the patch for this vulnerability. If immediate upgrade is not feasible, implement strict validation on all redirect/callback parameters to ensure they only allow trusted targets, and consider disabling the redirect functionality until the patch can be applied.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-0667 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-0667 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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