dbcve.org
Pdf Viewer MacroApplication · Xwiki

CVE-2024-52299

HIGH · 7.5 CVSS v3.1 Published 2024-11-13
Fix available
A fix is available. Upgrade to 2.5.6 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
macro-pdfviewer is a PDF Viewer Macro for XWiki using Mozilla pdf.js. Any user with view right on XWiki.PDFViewerService can access any attachment stored in the wiki as the "key" that is passed to prevent this is computed incorrectly, calling skip on the digest stream doesn't update the digest. 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 confidence

The XWiki PDF Viewer macro (macro-pdfviewer) has an access control bypass where the 'key' used to restrict attachment access is computed incorrectly. Specifically, calling skip on the digest stream fails to update the digest, allowing any user with view rights on XWiki.PDFViewerService to access any wiki attachment regardless of proper permissions.

MitigationUpgrade macro-pdfviewer to version 2.5.6 or later to resolve the digest computation issue that allows unauthorized attachment access.

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
Pdf Viewer MacroApplication
Affected:< 2.5.6

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

CVSS:3.1/AV:N/AC:L/PR:N/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 the installed PDF Viewer macro version
    In the XWiki administration interface, go to Extension Manager and search for 'PDF Viewer' or 'macro-pdfviewer'. Note the installed version number.
    Affected if The version is lower than 2.5.6 (for example, 2.5.5, 2.5.4, etc.)
  2. Confirm the macro is actively enabled
    Navigate to XWiki Administration > Content > Macros and verify that the PDF Viewer macro is listed as enabled, or check if any wiki pages use the PDF Viewer macro (search for '{{pdfViewer}}' in wiki content).
    Affected if The PDF Viewer macro is enabled and used in the wiki
  3. Check permissions on XWiki.PDFViewerService
    Go to the XWiki.PDFViewerService page object permissions (usually at /xwiki/bin/view/PDFViewerService?editor=object) and review which users or groups have View rights.
    Affected if Users other than administrators have View rights on this service document
  4. Verify attachment access controls are bypassed
    As a low-privilege user with only View rights on PDFViewerService but no rights on a restricted attachment, attempt to reference that attachment using the PDF Viewer macro to see if the content loads.
    Affected if The restricted attachment content loads despite the user lacking direct attachment permissions

You are affected if the PDF Viewer macro version is below 2.5.6 AND the macro is enabled, allowing any user with View rights on PDFViewerService to access attachments they should not have permission to view.

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 2.5.6 or later
Fixed in 2.5.6
Interim mitigation

Upgrade macro-pdfviewer to version 2.5.6 or later to resolve the digest computation issue that allows unauthorized attachment access.

Recommended fix Moderate confidence

Upgrade to macro-pdfviewer version 2.5.6

  1. 1. Identify all XWiki instances using the Pdf Viewer Macro
  2. 2. Check the current installed version of the macro-pdfviewer package
  3. 3. Review the XWiki upgrade documentation for your specific installation type
  4. 4. Upgrade the macro-pdfviewer to version 2.5.6 or later
  5. 5. Verify the upgrade was successful by checking the macro version
  6. 6. Test that the PDF viewer functionality works correctly post-upgrade
  7. 7. Confirm the vulnerability is remediated by verifying the key computation is now correct

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

Fix this in Pdf Viewer Macro Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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