PDFCrowd Blog

WordPress Plugins updated to 4.5.6

We have released a new version of our Save as PDF and Save as Image WordPress plugins.

Fixed:

  • Reflected cross-site scripting (XSS) vulnerability when the plugin is used in demo mode without an API key configured (CVE-2026-0862, low severity).

PDFCrowd WebSave updated to 1.3.0

We have released a new version of our WebSave product.

Version 1.3.0

New Features

  • window.WebSave.initButton(element) - Manually initialize buttons added to the page after WebSave loads. Required for single-page applications and dynamically generated content.
    Example:
    window.WebSave.initButton(document.querySelector('.my-button'))

Migrating from Save to PDF Link to WebSave as PDF

This guide helps you migrate from the Save to PDF Link service to WebSave as PDF. The migration is straightforward and can be completed in a few simple steps.

Why migrate? Save to PDF Link is a legacy service that relies on the HTTP referrer header, which is increasingly unreliable due to browser privacy features and HTTPS policies. WebSave as PDF works more reliably and offers better customization options.

Introducing WebSave

Today we're launching WebSave, a JavaScript library that adds PDF and image export capabilities to any website with just a few lines of code.

For current setup instructions, see WebSave as PDF to add a Save as PDF button to your website, or WebSave as Image to add a Save as Image button.

API clients 6.5.0 and WordPress 4.5.0

We have released version 4.5.0 of our WordPress Plugins and 6.5.0 of our API client libraries.

New:

  • The error handling system has been updated. This includes revised status codes and messages, as well as the addition of new methods to the error class: getStatusCode(), getReasonCode(), and getDocumentationLink(). The getCode() method is deprecated and should be replaced with getStatusCode().