CVE-2025-10186

WhyDonate – FREE Donate button – Crowdfunding – Fundraising <= 4.0.15 - Missing Authorization to Unauthenticated wp_wdplugin_style Rww Deletion

2025-10-14 19:46
Jonas Benjamin Friedli

Strategic Overview

Status
Patched in 4.0.16
Affected Version
<= 4.0.15
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-10186
View all WhyDonate – FREE Donate button – Crowdfunding – Fundraising vulnerabilities

At a glance

CVE-2025-10186 is a medium-severity Missing Authorization vulnerability in the WhyDonate WordPress plugin, affecting versions <= 4.0.15. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.0.16; sites on affected versions should update now. Disclosed October 2025, reported by Jonas Benjamin Friedli.

Vulnerability Overview

The WhyDonate – FREE Donate button – Crowdfunding – Fundraising plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the remove_row function in all versions up to, and including, 4.0.15. This makes it possible for unauthenticated attackers to delete rows from the wp_wdplugin_style table.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in WhyDonate <= 4.0.15 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WhyDonate the fix is 4.0.16: builds <= 4.0.15 are affected, anything from 4.0.16 onward is not.

Remediation

Update to version 4.0.16, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: WhyDonate 4.0.16 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Other vulnerabilities in WhyDonate – FREE Donate button – Crowdfunding – Fundraising

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C