Skip to main content
Mallory
MediumVulnerability

CVE-2007-1540: Directory Traversal in SQL-Ledger and LedgerSMB am.pl

Published Mar 20, 2007 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS4.3Medium · v2
EPSS5.1%93rd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendors
LedgersmbSql-Ledger
IdentifiersCVE-2007-1540CWE-22

A directory traversal vulnerability exists in am.pl in SQL-Ledger 2.6.27 and earlier, and in LedgerSMB before 1.2.0. The vulnerability allows remote attackers to execute arbitrary files and bypass authentication by supplying a crafted login parameter containing a '..' (dot dot) sequence and a trailing NULL byte (%00). Although SQL-Ledger 2.6.27 reportedly addressed the issue, third-party analysis indicates that file execution is still possible despite an error being generated.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote attackers to execute arbitrary executables on the server, potentially leading to full system compromise and bypass of authentication mechanisms.

Mitigation

If you can’t patch tonight, do this now.

Restrict access to the affected scripts at the web server level, validate and sanitize all user input, and monitor for suspicious login attempts containing directory traversal patterns or null bytes.

Remediation

Patch, then assume compromise.

Upgrade to a version of SQL-Ledger later than 2.6.27 and LedgerSMB 1.2.0 or later, ensuring that the patch fully addresses the directory traversal and null byte injection issues. Verify that the login parameter is properly sanitized and that user input cannot influence file paths.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
LedgersmbLedgersmbapplication
Sql-LedgerSql-Ledgerapplication
FAQ

Frequently asked questions

Is CVE-2007-1540 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2007-1540 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2007-1540?
As of Oct 16, 2026, Mallory has not confirmed a public exploit for CVE-2007-1540. 1 candidate exploit record is not yet analyzed.
Is there a patch for CVE-2007-1540?
Upgrade to a version of SQL-Ledger later than 2.6.27 and LedgerSMB 1.2.0 or later, ensuring that the patch fully addresses the directory traversal and null byte injection issues. Verify that the login parameter is properly sanitized and that user input cannot influence file paths.
What products are affected by CVE-2007-1540?
Ledgersmb and Sql-Ledger.
How severe is CVE-2007-1540?
CVE-2007-1540 has a CVSS v2 score of 4.3 (Medium) and an EPSS score of 5.1% (93rd percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.