CVE-2024-51446
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 · uneditedA vulnerability has been identified in Polarion V2310 (All versions), Polarion V2404 (All versions < V2404.4). The file upload feature of the affected application improperly sanitizes xml files. This could allow an authenticated remote attacker to conduct a stored cross-site scripting attack by uploading specially crafted xml files that are later downloaded and viewed by other users of the application.
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 confidenceStored cross-site scripting (XSS) vulnerability in Polarion's file upload functionality. The application fails to properly sanitize XML files during upload, allowing authenticated attackers to embed malicious scripts that execute when other users download and view the crafted XML files.
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>= 2404.0, < 2404.4= 2310.0CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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.
-
Determine installed Polarion versionAccess the Polarion administration panel or check the product version information typically found in the Help > About section, or inspect the polarion.properties/version file in the installation directoryAffected if The installed version is 2310.0 OR falls within 2404.0 through 2404.3 (anything less than 2404.4)
-
Verify XML file upload capability is accessibleLog in as an authenticated user with standard or elevated privileges and attempt to access the file upload functionality (typically found in Documents, Work Items, or Requirements modules)Affected if Authenticated users can upload files to the Polarion system
-
Confirm XML automatic rendering or preview is enabledCheck the Polarion configuration settings for XML file handling - look for options related to XML preview, automatic rendering, or inline XML viewing in the administration or user preferencesAffected if Automatic XML rendering or preview is enabled, allowing inline viewing of uploaded XML files without requiring a download
-
Check if Content Security Policy headers are configuredInspect the web server or Polarion configuration for Content-Security-Policy headers, or use browser developer tools to examine response headers when accessing PolarionAffected if No Content-Security-Policy headers are configured, or headers do not include 'script-src' restrictions that would block inline script execution
A user is affected if they run Polarion version 2310.0 or any version from 2404.0 to 2404.3, have authenticated file upload access, and have XML preview/rendering enabled without CSP protections.
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.
dbcve · scoped2404.4
Upgrade to Polarion V2404.4 or later. As an interim measure, consider disabling automatic XML rendering/preview in the application and implementing Content Security Policy headers to mitigate script execution.
V2404.4 or later (for V2404 line); contact vendor for V2310 fix
- 1. Identify the currently installed Polarion version by checking the application header or administration console
- 2. For users on Polarion V2404.x versions prior to V2404.4: Plan an upgrade to V2404.4 or later as the fixed release
- 3. For users on Polarion V2310: Contact Siemens customer support to confirm if a patch or newer fixed version is available for this release line
- 4. After upgrading to the fixed version, verify the XML file upload functionality works as expected
- 5. Test that uploaded XML files are properly sanitized and no longer allow script execution
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51446 — 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-2024-51446 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