CVE-2026-0862
Reflected XSS in PDFCrowd Save as PDF Plugin
Publication date: 2026-01-24
Last updated on: 2026-01-24
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| pdfcrowd | save_as_pdf_plugin | to 4.5.5 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-0862 is a Reflected Cross-Site Scripting (XSS) vulnerability in the Save as PDF Plugin by PDFCrowd for WordPress, affecting all versions up to 4.5.5. It occurs due to insufficient input sanitization and output escaping of the 'options' parameter. This allows unauthenticated attackers to inject malicious scripts that execute when a user is tricked into clicking a crafted link. Exploitation requires the PDFCrowd API key to be blank or set to the default 'demo mode'. The vulnerability was fixed in version 4.5.6 by changing how the encryption key is generated and used, replacing empty or predictable keys with a random 32-character secret to prevent manipulation. [1]
How can this vulnerability impact me? :
This vulnerability can allow attackers to execute arbitrary scripts in the context of the affected website, potentially leading to theft of user credentials, session hijacking, or performing actions on behalf of the user without their consent. Since it is a reflected XSS, attackers must trick users into clicking malicious links. The impact is limited to cases where the API key is blank or in demo mode, but if exploited, it can compromise user trust and site security. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect this vulnerability by checking if your WordPress installation uses the Save as PDF by PDFCrowd plugin version 4.5.5 or earlier and if the PDFCrowd API key is empty or set to 'demo' mode. There are no specific network detection commands provided, but you can verify the plugin version via WordPress admin or by running commands such as 'wp plugin list' to check the version. Additionally, inspecting the plugin settings for the API key value can help identify if it is blank or 'demo'. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediately update the Save as PDF by PDFCrowd plugin to version 4.5.6 or later, which fixes the vulnerability by preventing the use of an empty or 'demo' API key and instead generates a random encryption secret. Also, ensure that the PDFCrowd API key is set to a valid, non-demo value to avoid exploitation. [1]