OneSignal – Web Push Notifications <= 3.6.1 - Missing Authorization to Unauthenticated Plugin Settings Update
Strategic Overview
- Status
- Patched in 3.6.2
- Affected Plugin
- OneSignal – Web Push Notifications
- Affected Version
<= 3.6.1- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-13950
At a glance
CVE-2025-13950 is a medium-severity Missing Authorization vulnerability in the OneSignal WordPress plugin, affecting versions <= 3.6.1. 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 3.6.2; sites on affected versions should update now. Disclosed December 2025, reported by Marcin Dudek (dudekmar).
Vulnerability Overview
The OneSignal – Web Push Notifications plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the settings handling functionality in all versions up to, and including, 3.6.1. This is due to the plugin processing POST requests without verifying user capabilities or nonces. This makes it possible for unauthenticated attackers to overwrite the OneSignal App ID, REST API key, and notification behavior via direct POST requests.
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 OneSignal <= 3.6.1 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 OneSignal the fix is 3.6.2: builds <= 3.6.1 are affected, anything from 3.6.2 onward is not.
Remediation
Update to version 3.6.2, 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: OneSignal 3.6.2 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in OneSignal – Web Push Notifications
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C