HomeWordPress vulnerabilitiesSave as PDF Plugin by PDFCrowd
Save as PDF Plugin by PDFCrowd vulnerabilities
Save as PDF Plugin by PDFCrowd has 4 known vulnerabilities in this database. The most recent published record is dated 19 Sep 2026.
- Known vulnerabilities
- 4
- Active installs
- 1,000+
- Latest version
- 4.6.3
- Last updated
- 22 Sep 2026
- Most recent
- 19 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Remote code execution CVE-2026-92807 | High 8.8 | Up to 4.6.1 | Fixed in a later version (latest 4.6.3) | 19 Sep 2026 |
| Cross-site scripting (XSS) CVE-2026-0862 | Medium 6.1 | Up to 4.5.5 | Fixed in a later version (latest 4.6.3) | 24 Jan 2026 |
| Cross-site scripting (XSS) CVE-2024-10891 | Medium 6.4 | Before 4.2.2 | Fixed in 4.2.2 | 20 Nov 2024 |
| Cross-site scripting (XSS) CVE-2023-5971 | Medium 4.8 | Before 3.2.0 | Fixed in 3.2.0 | 14 May 2024 |
Read the published descriptions
- CVE-2026-92807, 19 Sep 2026
- The Save as PDF Plugin by PDFCrowd plugin for WordPress is vulnerable to Arbitrary Function Invocation in all versions up to, and including, 4.6.1 via the `pdf_created_callback` shortcode attribute. The `eval_shortcode()` function copies any non-`button_`/non-`email_` shortcode attribute verbatim into a custom options array without sanitization, allowlist enforcement, or capability checks, and `create_button()` AES-encrypts that array - including the attacker-supplied callback value - and embeds the resulting blob in the rendered button HTML; when the blob is later POSTed to the unauthenticated `wp_ajax_nopriv_save_as_pdf_pdfcrowd` endpoint, `save_as_pdf_pdfcrowd()` decrypts it and invokes `$options['pdf_created_callback']` as a PHP callable at line 1722 with no `is_callable()` guard, no allowlist, and no capability check. This makes it possible for authenticated attackers, with Contributor-level access and above, to invoke arbitrary PHP functions or static class methods with plugin option data as the sole argument, enabling disclosure of the site's stored PDFCrowd API key and username or further server-side abuse. Note that the encryption boundary does not mitigate this vector because the server itself encrypts the attacker-chosen callback during shortcode rendering, supplying any authenticated Contributor with a cryptographically valid blob that any unauthenticated visitor can subsequently replay to trigger invocation. CVE record
- CVE-2026-0862, 24 Jan 2026
- The Save as PDF Plugin by PDFCrowd plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the ‘options’ parameter in all versions up to, and including, 4.5.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. NOTE: Successful exploitation of this vulnerability requires that the PDFCrowd API key is blank (also known as "demo mode", which is the default configuration when the plugin is installed) or known. CVE record
- CVE-2024-10891, 20 Nov 2024
- The Save as PDF Plugin by Pdfcrowd plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'save_as_pdf_pdfcrowd' shortcode in all versions up to, and including, 4.2.1 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2023-5971, 14 May 2024
- The Save as PDF Plugin by Pdfcrowd WordPress plugin before 3.2.0 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup) CVE record
What to do if you run Save as PDF Plugin by PDFCrowd
If you run Save as PDF Plugin by PDFCrowd, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Save as PDF Plugin by PDFCrowd vulnerabilities
Free. We email you when a new vulnerability is published for Save as PDF Plugin by PDFCrowd, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.