CVE-2024-33684
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 · uneditedMissing Authorization vulnerability in Pdfcrowd Save as PDF plugin by Pdfcrowd allows Stored XSS.This issue affects Save as PDF plugin by Pdfcrowd: from n/a through 3.2.0.
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 confidenceMissing authorization in the Pdfcrowd Save as PDF plugin allows attackers to inject and store malicious scripts (Stored XSS). The vulnerability stems from insufficient access control checks, enabling authenticated users to inject persistent scripts that execute when other users view generated PDF content.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L
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.
-
Locate the Pdfcrowd Save as PDF pluginIn your WordPress admin panel, navigate to Plugins > Installed Plugins and locate the 'Pdfcrowd Save as PDF' plugin. Alternatively, check the plugin directory (wp-content/plugins/) for a folder containing 'pdfcrowd' in the name.Affected if The plugin is installed and active in your WordPress environment.
-
Identify the installed plugin versionIn the WordPress plugins list, click on the plugin to view its details, or open the main plugin PHP file (usually pdfcrowd.php or similar) and look for a version comment or defined constant near the top of the file.Affected if The version number displayed is lower than 3.2.0, or no version is displayed and the plugin has not been updated recently.
-
Verify the plugin is enabled for PDF generationCheck if the plugin is activated in WordPress admin under Plugins and confirm that the PDF generation feature is being used (look for any Save as PDF buttons or shortcodes added to posts/pages).Affected if The plugin is activated and users can generate PDFs through it.
-
Check for the presence of authorization checks on plugin endpointsIf you have code access, examine the main plugin PHP file for functions handling PDF generation requests and look for capability checks (such as current_user_can, check_admin_referer, or nonce verification) before processing user input.Affected if The code lacks authorization verification on endpoints that accept user input for PDF content (version below 3.2.0 typically lacks this).
Your environment is affected if the Pdfcrowd Save as PDF plugin is installed, active, and running at a version prior to 3.2.0.
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 dataUpdate to the latest version if available (3.2.0+) which should contain the authorization fix. If no patch exists, implement proper authorization checks on all plugin endpoints and sanitize all user inputs before rendering in PDF output.
- Consultation3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-33684 — 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-33684 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