CVE-2024-50803
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 · uneditedThe mediapool feature of the Redaxo Core CMS application v 5.17.1 is vulnerable to Cross Site Scripting(XSS) which allows a remote attacker to escalate privileges
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 confidenceCross-Site Scripting (XSS) vulnerability in the mediapool feature of Redaxo Core CMS v5.17.1 allows remote attackers to inject malicious scripts. The medium severity (CVSS 5.4) indicates user interaction is required but the impact includes privilege escalation, suggesting a stored XSS that targets administrative users accessing the mediapool.
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= 5.17.1CVSS 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.
-
Confirm Redaxo CMS installationIdentify whether your web application is built on Redaxo Core CMS by checking for Redaxo-specific files, headers, or the characteristic URL patterns (e.g., /redaxo/index.php).Affected if Your system is not running Redaxo CMS - this vulnerability only applies to Redaxo Core CMS.
-
Determine the installed Redaxo versionLocate the version file or admin panel version display. In Redaxo, the version is typically shown in the admin dashboard footer or can be found in a VERSION file in the installation root directory.Affected if The installed version is exactly 5.17.1 - this is the only version listed as affected in the CVE data.
-
Verify mediapool feature is accessibleAccess the mediapool module through the Redaxo admin interface (typically at /redaxo/index.php?page=mediapool or similar path) or check the module configuration to see if mediapool is enabled in your installation.Affected if The mediapool feature is enabled and accessible to users - the XSS flaw exists specifically within this feature.
-
Check for administrative or privileged usersReview the user management section to identify users with mediapool access permissions, particularly administrators or editors who would interact with the mediapool interface.Affected if There are users with access to the mediapool feature - the stored XSS would target these users when they access uploaded media.
You are affected only if you are running Redaxo Core CMS version 5.17.1 with the mediapool feature enabled and users who have access to it.
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 the patched version of Redaxo Core CMS. Until then, disable the mediapool feature for untrusted users and implement Content Security Policy headers to mitigate script injection.
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50803 — 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-50803 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