Raptive Ads <= 3.6.3 - Missing Authorization to Unauthenticated Data/Settings Reset
Strategic Overview
- Status
- Patched in 3.7.1
- Affected Plugin
- Raptive Ads
- Affected Version
<= 3.6.3- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-13364
At a glance
CVE-2024-13364 is a medium-severity Missing Authorization vulnerability in the Raptive Ads WordPress plugin, affecting versions <= 3.6.3. 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.7.1; sites on affected versions should update now. Disclosed February 2025, reported by Tieu Pham Trong Nhan.
Vulnerability Overview
The Raptive Ads plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on the site_ads_files_reset() and cls_file_reset() functions in all versions up to, and including, 3.6.3. This makes it possible for unauthenticated attackers to reset the ad and cls files.
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
Raptive Ads <= 3.6.3 carries this weakness at site_ads_files_reset(), and reaching it 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 Raptive Ads the fix is 3.7.1: builds <= 3.6.3 are affected, anything from 3.7.1 onward is not.
Remediation
Update to version 3.7.1, 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: Raptive Ads 3.7.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C