CVE-2026-54822
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 · uneditedSubscriber SQL Injection in SALESmanago & Leadoo <= 3.11.2 versions.
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 confidenceSQL injection vulnerability in SALESmanago and Leadoo platforms affecting subscriber functionality in versions 3.11.2 and below. Attackers can inject malicious SQL queries through subscriber input fields, potentially allowing unauthorized data access, modification, or extraction from the database.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L
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 platformDetermine whether your environment runs SALESmanago or Leadoo marketing automation platform. Check product documentation, installed software inventory, or system files for platform identification.Affected if The platform is SALESmanago or Leadoo and matches the version criteria below.
-
Check installed version numberLocate the version number of your SALESmanago or Leadoo installation. This is typically found in the admin dashboard (about/settings section), configuration files, or the software bill of materials. Compare your version against the affected range of 3.11.2 and below.Affected if The installed version is 3.11.2 or any version lower than 3.11.2.
-
Verify subscriber functionality is activeCheck if the subscriber management module is enabled in your platform configuration. This includes checking whether subscriber signup, import, or management features are accessible through the web interface or API.Affected if Subscriber functionality is enabled and accessible to end users or API consumers.
-
Inspect input handling for subscriber fieldsReview the application code or configuration that processes subscriber input fields (such as email, name, or custom fields). Determine whether raw user input is passed directly to SQL queries without parameterized queries or prepared statements.Affected if User-supplied subscriber data is concatenated directly into SQL queries without sanitization or parameter binding.
-
Review application logs for suspicious SQL patternsExamine web application logs, database logs, or WAF logs for unusual SQL syntax or keywords in subscriber-related request parameters that may indicate exploitation attempts.Affected if Log analysis reveals SQL injection payloads in subscriber input parameters.
If your environment runs SALESmanago or Leadoo version 3.11.2 or below with subscriber functionality enabled and direct SQL query construction, the environment is affected by this vulnerability.
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 a patched version > 3.11.2; implement parameterized queries or prepared statements for all database operations involving user input; apply input validation and escaping as an additional layer of defense.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-54822 — 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-2026-54822 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