On this page (7 sections)

A critical vulnerability, CVE-2026-19803, affects the Printcart Store - Web to Print Product Designer for WooCommerce plugin for WordPress in all versions up to and including 2.13.2. According to the NVD record, an unauthenticated visitor can write attacker-controlled PHP content to arbitrary locations outside the uploads directory, which can result in remote code execution when the written file is requested.

If you run a WooCommerce store that offers product customization with this plugin, check your version and one specific setting today. The NVD describes the unauthenticated attack path as depending on a particular configuration, which makes a quick check worthwhile.

What happened

The vulnerability was published on 2026-11-07 in the NVD. The description attributes the problem to an AJAX handler named nbu_crop_image that accepts a user-supplied url parameter and does not normalize or strip ../ sequences. As a result, a remote, unauthenticated attacker can cause attacker-controlled PHP content to be written to a location outside the uploads directory, and the NVD says code execution follows when that file is subsequently requested.

Only one independent publisher covers this story so far, in addition to the NVD entry itself. The references include a plugin repository changeset and a Wordfence threat intelligence entry. The research does not name a patched version and contains no report of attacks in the wild, so treat both the fix status and the exploitation status as unconfirmed.

Technical details in plain terms

This is a path traversal problem combined with unrestricted file writing. According to the NVD description, the plugin builds a file path by appending the attacker-supplied url value onto the uploads base directory without normalizing it or removing ../ sequences. It then derives both the output directory and the output file extension from that same attacker-controlled path.

The description also notes that no stripImage() call is made before writeImage() is invoked. In plain terms, the handler is expected to process an image but does not clean it, so attacker-controlled PHP content can be written to arbitrary locations outside the uploads directory. The NVD states that remote code execution results when the written file is subsequently requested.

Why the configuration condition matters

The NVD says the vulnerability is only exploitable when the nbdesigner_upload_popup_style site option is set to a, the Advanced Upload Popup, which causes the handler to be registered for unauthenticated requests. The description adds that the required save-design nonce is printed on the public upload-design-file frontend page. A nonce is a token meant to protect an action, but here any anonymous visitor can read it, so it is not a real barrier once that configuration is active.

Who is affected

Any site running the plugin at version 2.13.2 or earlier is in the affected range. The realistically exposed group is stores where the Advanced Upload Popup style is enabled, because that is the configuration the NVD ties to the unauthenticated exploit path. The research does not say whether other configurations are safe or whether logged-in users can reach the handler, so do not assume that a different setting makes the plugin safe. Updating or removing it remains the sound choice once a fix is available.

How to check your exposure

First confirm whether the plugin is installed and which version it runs. This read-only WP-CLI command lists plugins with their versions and status; look for the Printcart entry and compare it with 2.13.2.

List installed plugins and versions (run from the WordPress root)WP-CLI
wp plugin list --fields=name,status,version

Next, check the option the NVD description names. This read-only command prints its current value. A result of a means the configuration described in the NVD is active.

Read the upload popup style option (run from the WordPress root)WP-CLI
wp option get nbdesigner_upload_popup_style

Then look for signs of misuse. AJAX action names are normally sent in a POST body, which web server access logs do not record by default, so searching logs for nbu_crop_image can miss real attacks. A clean result does not prove your site is safe. A more useful read-only check is to look for direct requests to PHP files in places where none should be requested, such as the uploads directory. This grep lists access log lines that request a .php file under wp-content/uploads; any hit deserves a closer look. The log path is only an example, so adjust it for your server.

Find requests for PHP files under uploads, nginx example pathShell
grep -E "/wp-content/uploads/.*\.php" /var/log/nginx/access.log
Find requests for PHP files under uploads, Apache example path (Debian/Ubuntu)Shell
grep -E "/wp-content/uploads/.*\.php" /var/log/apache2/access.log

Because the flaw can write files outside the uploads directory, also search the filesystem. This read-only command lists PHP files under wp-content/uploads from the WordPress root; legitimate sites rarely have any, so investigate every result.

List PHP files inside the uploads directory (run from the WordPress root)Shell
find wp-content/uploads -type f -name "*.php"

What to do now

  1. Identify every site where the Printcart plugin is installed and note its version.
  2. Check whether nbdesigner_upload_popup_style is set to a on each site.
  3. If a patched release is published, back up the site and update. The research does not name a fixed version, so check the plugin's official page and changelog.
  4. Until you can update, consider deactivating the plugin, after testing the effect on your customizer workflow. Changing the popup style may reduce exposure to the path the NVD describes, but the research does not confirm that other settings are safe.
  5. Search the web root and uploads folders for unexpected .php files, especially outside wp-content/uploads or with image-like names.
  6. Review access logs for direct requests to unexpected PHP files, keeping in mind that POST bodies are not logged by default.
  7. If you find a suspicious file, treat the site as compromised: preserve evidence, rotate credentials and secrets, and restore from a clean backup.
Caution. Deactivating a plugin on a live store can break product customization and affect orders in progress. Test on a staging copy or schedule it for a quiet period, and take a full backup first.
Tip. A web application firewall rule that blocks path traversal sequences in request parameters can add a layer of defense, but it is not a substitute for updating or removing the vulnerable plugin.

Detection and monitoring

Because the end result of this flaw is a PHP file appearing somewhere it should not, file integrity checks are your best signal. Compare the file list on the server against a known-good baseline, and alert on new executable files in upload directories. Our guide on how to check if a website is hacked walks through the common signs, and what outside-in malware detection can and cannot see explains the limits of scanning from the outside.

It also helps to track plugin vulnerabilities over time. You can look up known issues per plugin on the WordPress plugin vulnerability list and review the WordPress security checklist for habits such as removing unused plugins and limiting who can write to the web root.

What is still unknown

  • No fixed version is named in the research.
  • The research contains no report of in-the-wild exploitation and the CVE is not in CISA KEV, so exploitation status is unconfirmed rather than ruled out.
  • Coverage is thin: the details come from the NVD record and linked references, with only one independent publisher so far.
  • The CVSS 9.8 score appears in the NVD record data; the research does not say which organization assigned it.

Treat the situation as developing. Recheck the plugin's changelog and the references above for a patched release.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-19803: The Printcart Store – Web to Print Product Designer for WooCommerce plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to, and…nvd.nist.gov ·
  • WordPress
  • WooCommerce
  • CVE-2026-19803
  • File upload
  • RCE