CVE-2007-1923
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(1) LedgerSMB and (2) DWS Systems SQL-Ledger implement access control lists by changing the set of URLs linked from menus, which allows remote attackers to access restricted functionality via direct requests. The LedgerSMB affected versions are before 1.3.0.
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 confidenceThis vulnerability stems from LedgerSMB and SQL-Ledger implementing access control solely by hiding menu links to restricted functionality, rather than enforcing proper server-side authorization. An attacker who knows or guesses the direct URLs to sensitive functions can bypass the access restrictions entirely, as no authentication or authorization checks are performed on direct requests.
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.3.0all versionsCVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/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 the installed product and versionCheck the application banner, about page, or version file. For LedgerSMB, look for a version indicator in the login page source, README, or changelog file. For SQL-Ledger, check the admin interface or documentation.Affected if The product is LedgerSMB version < 1.3.0, or any version of SQL-Ledger.
-
Locate the application's direct URL endpointsExamine the application's directory structure for CGI/Perl scripts (typically in a 'bin' or 'scripts' directory). Common sensitive endpoints include admin functions, user management, and reporting modules.Affected if The application uses direct CGI script URLs for sensitive functions (common in LedgerSMB/SQL-Ledger).
-
Test direct URL access to sensitive functionsAttempt to access known sensitive endpoints directly via browser or curl (e.g., admin.pl, users.pl, or similar admin-related scripts) WITHOUT logging in or using an authenticated session.Affected if The sensitive endpoints return actual content or functionality rather than redirecting to a login page or returning an authorization error.
-
Verify authorization is enforced server-sideLog in with a restricted (non-admin) user account, then attempt to access admin-level functions by constructing the direct URL to those functions.Affected if The restricted user can access admin functions via direct URL when they should be denied, indicating server-side authorization checks are missing.
-
Confirm menu hiding is the only access controlCompare the access restrictions in the application's menu configuration or role-based access control files against actual server-side permission checks in the code.Affected if Menu links are hidden for restricted users but the underlying scripts do not validate user permissions before executing sensitive operations.
A user is affected if they are running LedgerSMB < 1.3.0 or any SQL-Ledger version AND sensitive functions are accessible via direct URL without proper authentication or authorization checks.
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 data1.3.0
Implement server-side authorization checks on all sensitive endpoints and functions, regardless of whether they are accessible via menu links. Enforce proper role-based access control (RBAC) at the application layer for every protected resource.
- Consultation6.0 h
- Implementation20.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,232.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-1923 — 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-1923 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