CVE-2025-56450
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 · uneditedLog2Space Subscriber Management Software 1.1 is vulnerable to unauthenticated SQL injection via the `lead_id` parameter in the `/l2s/api/selfcareLeadHistory` endpoint. A remote attacker can exploit this by sending a specially crafted POST request, resulting in the execution of arbitrary SQL queries. The backend fails to sanitize the user input, allowing enumeration of database schemas, table names, and potentially leading to full database compromise.
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 confidenceLog2Space Subscriber Management Software 1.1 contains an unauthenticated SQL injection vulnerability in the /l2s/api/selfcareLeadHistory endpoint via the lead_id parameter. Attackers can send specially crafted POST requests with malicious SQL payloads to execute arbitrary database queries, enabling enumeration of schemas and tables with potential full database compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
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.
-
Confirm Log2Space installation and versionLocate the Log2Space application installation directory or check the software inventory/system registry for 'Log2Space Subscriber Management Software' and note the installed version number. Compare against version 1.1.Affected if The software is installed and the version is 1.1.
-
Verify the affected endpoint existsAttempt to access the URL path /l2s/api/selfcareLeadHistory on the server (e.g., via curl or a browser). A 404 response indicates the endpoint may not exist, while other responses indicate it is available.Affected if The endpoint returns any response other than 404, meaning the vulnerable endpoint is present.
-
Check endpoint authentication requirementSend a POST request to /l2s/api/selfcareLeadHistory with a minimal payload (e.g., lead_id=1) without including any authentication tokens, cookies, or credentials. Observe whether the request is accepted or rejected.Affected if The endpoint accepts the request without requiring authentication, indicating the SQL injection is reachable without credentials.
-
Inspect application logs for SQL errorsReview application logs for any SQL syntax errors, database error messages, or unexpected query-related exceptions that may indicate SQL injection testing has occurred or the vulnerability is present.Affected if SQL error messages or database exception traces appear in logs related to the selfcareLeadHistory endpoint.
A user is affected if Log2Space Subscriber Management Software version 1.1 is installed, the /l2s/api/selfcareLeadHistory endpoint is accessible, and it can be reached without authentication.
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 dataReplace dynamic SQL queries with parameterized queries/prepared statements and implement proper input validation on the lead_id parameter. Apply principle of least privilege to the database user account.
- Consultation3.0 h
- Implementation6.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-56450 — 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-2025-56450 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