dbcve.org
Polarion AlmApplication · Siemens

CVE-2024-51445

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 affected application contains a XML External Entity Injection (XXE) vulnerability in the docx import feature. This could allow an authenticated remote attacker to read arbitrary data from the application server.

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

Polarion V2310 and V2404 versions prior to V2404.4 contain an XML External Entity Injection (XXE) vulnerability in the docx file import functionality. An authenticated attacker can craft a malicious docx file containing external entity references to read arbitrary files from the server's filesystem or perform server-side request forgery.

MitigationApply the vendor patch (V2404.4 or later) to disable external entity processing in the XML parser used by the docx import feature, or disable docx import until patching is feasible.

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 Polarion installation and version
    Locate the Polarion installation directory and check the version file or about page. Common locations include the installation root or admin interface showing the product version.
    Affected if The installed version is V2310.0 or any V2404.x version prior to V2404.4 (e.g., V2404.0, V2404.1, V2404.2, V2404.3).
  2. Confirm docx import functionality is accessible
    Check if the docx import feature is available in the web interface. Look for document import options in the Polarion UI or check for import-related API endpoints accessible to authenticated users.
    Affected if The docx import feature is enabled and accessible to authenticated users in the affected version.
  3. Verify authentication context
    Determine if there are user accounts with access to the docx import functionality. Check user roles and permissions related to document import capabilities.
    Affected if Authenticated users with import privileges exist in the system, as the XXE exploit requires authentication.
  4. Cross-reference build number with patch level
    If version shows V2404.x, check the build number or patch level to confirm whether it is V2404.4 or later. Earlier build numbers within V2404.x indicate an unpatched state.
    Affected if The build is earlier than the V2404.4 patch release, indicating the XXE mitigation is not applied.

A system is affected if it runs Polarion V2310.0 or any V2404.0-V2404.3 version, has the docx import feature accessible to authenticated users, and has not been updated to V2404.4 or later.

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 the vendor patch (V2404.4 or later) to disable external entity processing in the XML parser used by the docx import feature, or disable docx import until patching is feasible.

Recommended fix Moderate confidence

V2404.4

  1. 1. Identify the currently installed Polarion Alm version by checking the application or system information.
  2. 2. For version 2404.x (where x < 4): Upgrade to version 2404.4 or later to resolve the XXE vulnerability.
  3. 3. For version 2310.0: Contact Siemens customer support to confirm available remediation options, as no specific fixed version is documented in the advisory for this branch.
  4. 4. After upgrading, verify the docx import functionality works correctly.
  5. 5. Test that the XML External Entity Injection vulnerability is no longer exploitable.

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

Fix this in Polarion Alm Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,790
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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