dbcve.org
Polarion AlmApplication · Siemens

CVE-2024-51444

MEDIUM · 6.5 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 2404.4 or later.
See remediation →
71/100
Remediation priority · Elevated
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
A vulnerability has been identified in Polarion V2310 (All versions), Polarion V2404 (All versions < V2404.4). The application insufficiently validates user input for database read queries. This could allow an authenticated remote attacker to conduct an SQL injection attack that bypasses authorization controls and allows to download any data from the application's database.

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

A SQL injection vulnerability in Polarion V2310 (all versions) and V2404 (versions before V2404.4) allows authenticated remote attackers to inject malicious SQL through insufficiently validated user input in database read queries. This bypasses authorization controls and enables exfiltration of arbitrary data from the application's database.

MitigationApply vendor patch V2404.4 or later. Until then, implement strict input validation and refactor vulnerable database queries to use parameterized queries or prepared statements.

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
Polarion AlmApplication
Affected:>= 2404.0, < 2404.4= 2310.0

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checks

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

  1. Identify installed Polarion version
    Access the Polarion web interface and navigate to Administration > System Information, or check the installation directory for a version file. Alternatively, inspect the 'polarion.properties' or 'version.ini' file in the Polarion installation root directory.
    Affected if The installed version is exactly 2310.0, or falls within the range 2404.0 through 2404.3 (any version >= 2404.0 but < 2404.4).
  2. Verify web application accessibility
    Confirm that the Polarion web application (HTTP/HTTPS port, typically 8080 or 8443) is reachable from network locations where untrusted users could connect.
    Affected if The web interface is exposed to network access without proper firewall restrictions, allowing potential authenticated attackers to reach the application.
  3. Confirm user authentication is enabled
    Check that the Polarion authentication mechanism is active by attempting to log in or reviewing the 'security-config.xml' or 'polarion-config.xml' file for authentication settings.
    Affected if User authentication is enabled, as the SQL injection requires an authenticated session to exploit.

You are affected if your Polarion installation version is exactly 2310.0 or is any version from 2404.0 through 2404.3, and the web application is accessible to authenticated users.

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
Upgrade available Upgrade to 2404.4 or later
Fixed in 2404.4
Interim mitigation

Apply vendor patch V2404.4 or later. Until then, implement strict input validation and refactor vulnerable database queries to use parameterized queries or prepared statements.

Recommended fix High confidence

V2404.4 (for V2404.x branch); V2404.4 or later recommended for V2310 users

  1. 1. Identify the current Polarion version by checking the application administration panel or installation details.
  2. 2. For Polarion V2404.x instances: Plan an upgrade to V2404.4 or later, which contains the fix for this SQL injection vulnerability.
  3. 3. For Polarion V2310 instances: No specific fixed version is mentioned in the advisory. Consider upgrading to the latest available version or the V2404.x line (specifically V2404.4 or later) to remediate this vulnerability.
  4. 4. Schedule the upgrade during a planned maintenance window following standard Polarion upgrade procedures.
  5. 5. After upgrading, verify the application functions correctly and confirm the vulnerability is resolved by reviewing release notes or running internal security tests.
Caveat Standard Polarion upgrade procedures should be followed; review upgrade documentation for any configuration or compatibility considerations

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

Fix this in Polarion Alm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-51444 — 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-51444 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