dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2024-11504

HIGH · 8.6 CVSS v4.0 Published 2025-03-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
92/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Input from multiple fields in Streamsoft Prestiż is not sanitized properly, leading to an SQL injection vulnerability, which might be exploited by an authenticated remote attacker.  This issue was fixed in 18.1.376.37 version of the software.

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 confidence

Streamsoft Prestiż contains an SQL injection vulnerability in multiple input fields where user-supplied data is not properly sanitized before being used in database queries. An attacker with valid authentication credentials can inject malicious SQL statements through these fields to manipulate database queries, potentially exfiltrating, modifying, or deleting data. The vendor has addressed this issue in version 18.1.376.37.

MitigationUpgrade Streamsoft Prestiż to version 18.1.376.37 or later to incorporate the vendor's security fix. If immediate patching is not feasible, implement strict input validation and parameterized queries as a compensating control until the upgrade can be performed.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Streamsoft Prestiż installed version
    Locate the application installation directory or check the product's About/Version information panel within the software interface. Common locations include C:\Program Files\Streamsoft\Prestiż or the application's built-in version info accessed via Help > About. If installed as a service, check the service properties or configuration files for version metadata.
    Affected if The installed version is lower than 18.1.376.37 (e.g., 18.1.x versions before .37, or earlier major versions).
  2. Verify database query functionality is exposed
    Confirm that the application exposes web interfaces, API endpoints, or client forms that accept user input and construct database queries. These typically include search fields, filter parameters, report generation inputs, or data entry forms.
    Affected if The application has input fields that interact with the database and are accessible to authenticated users.
  3. Confirm authentication mechanism is in use
    Review the application's access control configuration to determine if user authentication is required to access the vulnerable input fields. Check user role definitions and session management settings.
    Affected if The vulnerable fields are accessible to users with standard authentication (not restricted to administrative roles only).

The environment is affected if Streamsoft Prestiż is installed at a version lower than 18.1.376.37 and authenticated users can access input fields that interact with database queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Streamsoft Prestiż to version 18.1.376.37 or later to incorporate the vendor's security fix. If immediate patching is not feasible, implement strict input validation and parameterized queries as a compensating control until the upgrade can be performed.

Recommended fix Moderate confidence

Upgrade to Streamsoft Prestiż version 18.1.376.37 or later

  1. Contact Streamsoft vendor to obtain version 18.1.376.37 or later of Streamsoft Prestiż
  2. Review official release notes for version 18.1.376.37 to understand any configuration or migration requirements
  3. Perform a complete backup of the current Streamsoft Prestiż database and configuration files
  4. Deploy and test the upgrade in a non-production/staging environment
  5. Schedule a maintenance window for the production environment upgrade
  6. Apply the version 18.1.376.37 upgrade to the production environment
  7. Verify the SQL injection vulnerability is fixed by testing the previously vulnerable input fields

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-11504 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-11504 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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