dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-30263

HIGH · 7.7 CVSS v3.1 Published 2024-04-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
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
macro-pdfviewer is a PDF Viewer Macro for XWiki using Mozilla pdf.js. Users with edit rights can access restricted PDF attachments using the PDF Viewer macro, just by passing the attachment URL as the value of the ``file`` parameter. Users with view rights can access restricted PDF attachments if they are shown on public pages where the PDF Viewer macro is called using the attachment URL instead of its reference. This vulnerability has been patched in version 2.5.1.

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 PDF Viewer macro in XWiki allows unauthorized access to restricted PDF attachments. Users with edit rights can bypass access controls by passing the attachment URL directly to the `file` parameter. Additionally, view-only users can access restricted PDFs when the macro is called with an attachment URL on public pages. This is an authorization bypass via improper reference validation.

MitigationUpgrade the macro-pdfviewer component to version 2.5.1 or later to apply the vendor patch. Review existing pages using the PDF Viewer macro to ensure restricted attachments are not exposed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Confirm XWiki installation
    Identify if XWiki is running in your environment. Check for XWiki web application files, services, or the presence of the XWiki database.
    Affected if XWiki is not installed - the vulnerability does not apply.
  2. Check macro-pdfviewer component version
    Locate and inspect the macro-pdfviewer component version in your XWiki installation. Compare the installed version against the fixed version 2.5.1. If using a package manager or XWiki extension manager, query the installed version of the PDF Viewer macro.
    Affected if The installed version is lower than 2.5.1, indicating the unpatched component is in use.
  3. Identify PDF Viewer macro usage
    Search your XWiki instance for pages or content that utilize the PDF Viewer macro. Look for wiki syntax or API calls containing 'pdfviewer' or the macro invocation. Check both page content and templates.
    Affected if The PDF Viewer macro is actively used on your XWiki instance.
  4. Review macro configuration for file parameter
    Inspect pages using the PDF Viewer macro for the 'file' parameter pointing to attachment URLs. Examine whether restricted PDF attachments are being referenced via direct URL parameters rather than through proper attachment selectors. Check macro configurations and page content for patterns like 'file=...'.
    Affected if The macro is configured with the 'file' parameter pointing directly to attachment URLs, enabling the authorization bypass path.

You are affected if your XWiki installation has the macro-pdfviewer component version below 2.5.1 AND the PDF Viewer macro is in use with the 'file' parameter exposing attachment URLs.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the macro-pdfviewer component to version 2.5.1 or later to apply the vendor patch. Review existing pages using the PDF Viewer macro to ensure restricted attachments are not exposed.

Recommended fix High confidence

Upgrade to macro-pdfviewer version 2.5.1 or later

  1. 1. Identify the currently installed version of macro-pdfviewer in the XWiki instance
  2. 2. Upgrade macro-pdfviewer to version 2.5.1 or later using the XWiki extension manager or the appropriate package manager
  3. 3. Verify the upgrade was successful by checking the installed version
  4. 4. Test that access controls on PDF attachments are properly enforced after the upgrade

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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