⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Medium · CVSS 6.4

How to Fix CVE-2026-4072: Critical Vulnerability in WordPress PayPal Donation

Other vulnerabilities in the same area that are worth patching alongside this one:

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 6.4 - Medium
Actively exploited?Not currently listed in CISA KEV
Affected0 <= 1.01
Fixed inSee vendor advisory
Type (CWE)CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

What is CVE-2026-4072?

CVE-2026-4072 is a security flaw in WordPress PayPal Donation. The WordPress PayPal Donation plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'donate' shortcode in all versions up to, and including, 1.01. This is due to insufficient input sanitization and output escaping on user-supplied shortcode attributes such as 'amount', 'email', 'title', 'return_url', 'cancel_url', 'ccode', and 'image'.

Why this CVE matters

Unpatched network-facing software is the leading initial-access vector in public breach reporting. Treat any CVSS-9 class flaw on an internet-reachable system as urgent, regardless of whether public exploit code has been observed yet.

For deployments of WordPress PayPal Donation that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Open WordPress PayPal Donation's About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.

How to fix CVE-2026-4072

  1. Read the vendor advisory in full: https://www.wordfence.com/threat-intel/vulnerabilities/id/99a8b48b-2967-4179-a0eb-626bbe273f03?source=cve
  2. Upgrade WordPress PayPal Donation to the patched build listed in the vendor advisory.
  3. Back up the configuration (and database, where applicable) before upgrading.
  4. Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
  5. Restart the affected service so the patched binary loads, then verify the new version (see verification section).

Update the WordPress plugin via WP-CLI


# CVE-2026-4072 affects WordPress PayPal Donation 0 <= 1.01. Fixed in version 1.01.
# Vendor advisory: https://www.wordfence.com/threat-intel/vulnerabilities/id/99a8b48b-2967-4179-a0eb-626bbe273f03?source=cve

# 1. Check the currently installed version of the plugin.
wp plugin get wordpress-paypal-donation --field=version

# 2. Update to the patched release named in the advisory.
wp plugin update wordpress-paypal-donation --version=1.01

# 3. Verify the update.
wp plugin get wordpress-paypal-donation --field=version
# The version must be >= 1.01 for the fix listed in the advisory.

# 4. If you cannot update right away, deactivate the plugin until you can.
wp plugin deactivate wordpress-paypal-donation


# Hosting-panel workflow (cPanel / Plesk / hosting dashboard):
# 1. WordPress -> Plugins -> Installed Plugins -> Update next to WordPress PayPal Donation.
# 2. Confirm the version under "Active Plugins" matches 1.01.


# Vendor advisory: https://www.wordfence.com/threat-intel/vulnerabilities/id/99a8b48b-2967-4179-a0eb-626bbe273f03?source=cve
# Trigger an SSH-driven update from a Windows admin workstation.
ssh wpadmin@<host> "wp plugin update wordpress-paypal-donation --version=1.01"
ssh wpadmin@<host> "wp plugin get wordpress-paypal-donation --field=version"

Verify the fix landed


# CVE-2026-4072 verification checklist.

# 1. Confirm the running version matches 1.01 (replace the version probe with
#    the platform-specific command shown above).

# 2. Re-scan the host with your vulnerability scanner (Nessus, Qualys, Tenable,
#    OpenVAS, Wazuh). The scanner must no longer flag CVE-2026-4072.

# 3. Inspect recent service and kernel logs for crash-loops or rollback events.
journalctl -u <service-name> --since "10 minutes ago"
dmesg --since "10 minutes ago"

# 4. Cross-check the running build against the vendor advisory:
#    https://www.wordfence.com/threat-intel/vulnerabilities/id/99a8b48b-2967-4179-a0eb-626bbe273f03?source=cve

If you cannot patch immediately

No official workaround exists beyond restricting network exposure to the affected component. Apply the vendor patch as the primary remediation.

How to verify the fix worked

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for log entries that do not match your normal request patterns, especially repeated requests to the same uncommon endpoint, and any administrative changes you cannot tie back to a known operator.

Frequently asked questions

Is CVE-2026-4072 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Will a WAF or IDS rule fully mitigate CVE-2026-4072?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for WordPress PayPal Donation run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*