Raptive AdsWordPress extension · Raptive
CVE-2024-13364
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Raptive Ads WordPress plugin lacks authorization checks on site_ads_files_reset() and cls_file_reset() functions, allowing any unauthenticated user to reset ad configuration files. This is a broken access control vulnerability where the plugin exposes sensitive reset functionality without verifying user identity or permissions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Raptive AdsWordPress extension
<= 3.6.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Raptive Ads plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Raptive Ads' or check the wp-content/plugins directory for a folder named 'ad-laterals' or similar Raptive-related folderAffected if The Raptive Ads plugin appears in the installed plugins list
-
Check installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins, find Raptive Ads, and note the version number displayed below the plugin nameAffected if The installed version is 3.6.3 or lower
-
Inspect plugin file for vulnerable functionsAccess the plugin files via FTP or file manager, locate the main plugin PHP file (usually in wp-content/plugins/[raptive-folder]/), and search for function names 'site_ads_files_reset' and 'cls_file_reset'Affected if These function definitions exist in the plugin files without capability checks (like 'current_user_can' or 'wp_verify_nonce')
-
Check for authorization callback in reset functionsOpen the file containing the reset functions and verify if the function body begins with a capability check such as 'if (!current_user_can('manage_options'))' or a nonce verificationAffected if No capability check or nonce verification is present before the reset logic executes
You are affected if the Raptive Ads plugin is installed with version 3.6.3 or lower and the reset functions lack authorization checks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the Raptive Ads plugin to version 3.6.4 or later which implements proper capability checks on the affected functions. Until then, consider disabling the plugin or restricting access at the web server level.
Fix this in Raptive Ads
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13364 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-13364 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data