CVE-2007-1329
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 · uneditedDirectory traversal vulnerability in SQL-Ledger, and LedgerSMB before 1.1.5, allows remote attackers to read and overwrite arbitrary files, and execute arbitrary code, via . (dot) characters adjacent to (1) users and (2) users/members strings, which are removed by blacklisting functions that filter these strings and collapse into .. (dot dot) sequences.
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 confidenceDirectory traversal vulnerability in SQL-Ledger and LedgerSMB before 1.1.5 allows remote attackers to read/write arbitrary files and execute code by exploiting blacklisting functions that filter dot characters. When dots adjacent to 'users' and 'users/members' strings are filtered, they collapse into '..' sequences, enabling path traversal.
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.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed LedgerSMB versionLocate the version file or check the login/admin interface for the LedgerSMB version number. Common locations include a VERSION file in the installation directory or the version displayed in the web interface footer.Affected if The installed version is 1.1.1 or earlier (any version <= 1.1.1)
-
Identify installed SQL-Ledger versionLocate the version file or check the login/admin interface for the SQL-Ledger version number. Common locations include a VERSION file in the installation directory or the version displayed in the web interface.Affected if The installed version is 2.6.25 exactly (version = 2.6.25)
-
Check for vulnerable dot-filtering codeInspect the source code files that handle file path operations, specifically looking for blacklisting functions that filter dot characters (.) in paths. Search for functions that process 'users' and 'users/members' path components.Affected if Blacklisting functions that filter dots are present in the codebase, and dots adjacent to 'users' or 'users/members' strings can collapse into '..' sequences
-
Verify web server file access configurationReview the web server configuration to determine which directories the application has read/write access to. Check if the web server user can access system files outside the intended application directory.Affected if The web server process has permissions to access directories outside the intended LedgerSMB/SQL-Ledger data directory
-
Inspect HTTP request handling for path parametersReview application logs and code to identify if user-supplied path parameters are processed without proper canonicalization. Look for file download or include functionality that uses path parameters.Affected if The application accepts path parameters in HTTP requests that are processed without allowlist validation and could contain '..' sequences after dot filtering
You are affected if running LedgerSMB <= 1.1.1 or SQL-Ledger 2.6.25 AND the application uses vulnerable blacklisting functions that filter dots in paths containing 'users' or 'users/members' strings.
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.
dbcve · scopedUpgrade to LedgerSMB 1.1.5 or later. If upgrade unavailable, implement proper path canonicalization with allowlist validation instead of blacklisting dot sequences, and restrict file operations to intended directories.
LedgerSMB 1.1.5 or later
- Upgrade LedgerSMB to version 1.1.5 or later to resolve the directory traversal vulnerability
- If using SQL Ledger 2.6.25, contact vendor for patch or consider upgrading to latest stable release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-1329 — 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-1329 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