CVE-2024-52300
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 · uneditedmacro-pdfviewer is a PDF Viewer Macro for XWiki using Mozilla pdf.js. The width parameter of the PDF viewer macro isn't properly escaped, allowing XSS for any user who can edit a page. XSS can impact the confidentiality, integrity and availability of the whole XWiki installation when an admin visits the page with the malicious code. This is fixed in 2.5.6.
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 confidenceThe macro-pdfviewer plugin for XWiki contains a stored XSS vulnerability in the width parameter. Attackers with page edit permissions can inject malicious JavaScript through the improperly escaped width parameter. When administrators view pages containing the malicious code, the XSS executes with elevated privileges, potentially allowing complete compromise of the XWiki installation.
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< 2.5.6CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
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.
-
Verify the PDF viewer macro is installedAccess XWiki Administration > Extensions and search for 'PDF Viewer Macro' or check the extension manager for installed macrosAffected if The macro-pdfviewer plugin appears in the installed extensions list
-
Determine the installed version of the PDF viewer macroIn the Extensions manager, locate the PDF Viewer Macro entry and note the version number shownAffected if The version listed is lower than 2.5.6 (for example, 2.5.5, 2.5.4, etc.)
-
Confirm users have page edit permissionsCheck XWiki's user rights configuration: go to Administration > Users > Rights and verify if non-admin users have Edit or Script permissions on any spacesAffected if Users other than administrators have edit rights, allowing them to insert malicious width parameters
-
Inspect existing pages using the PDF viewer macroSearch wiki pages for '{{pdfViewer}}' or 'pdfviewer' macro syntax and review the width parameter values in each usageAffected if Any page contains a width parameter with unusual characters (such as quotes, javascript:, or HTML tags) that suggest injection attempts
A user is affected if the macro-pdfviewer version is below 2.5.6 AND non-admin users have edit permissions that could allow them to inject malicious width parameters into PDF viewer macros.
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 · scoped2.5.6
Upgrade the macro-pdfviewer to version 2.5.6 or later, which contains proper escaping of the width parameter. Verify that PDF viewing functionality remains intact after the upgrade.
2.5.6
- Identify all XWiki installations using the Pdf Viewer Macro
- Locate the Pdf Viewer Macro dependency in your project's pom.xml, build configuration, or XWiki extension manager
- Update the Pdf Viewer Macro version to 2.5.6 or later
- Rebuild and redeploy the XWiki instance
- Verify the upgrade by checking the macro version in XWiki administration
- Clear any caching layers if applicable
- Test that the PDF viewer macro functions correctly with the new version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52300 — 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-52300 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