AdfoxlyWordPress extension · Wpfoxly
CVE-2024-34802
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 · uneditedMissing Authorization vulnerability in AdFoxly AdFoxly – Ad Manager, AdSense Ads & Ads.Txt.This issue affects AdFoxly – Ad Manager, AdSense Ads & Ads.Txt: from n/a through 1.8.5.
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 · moderate confidenceThe AdFoxly WordPress plugin (versions up to 1.8.5) contains a missing authorization vulnerability allowing unauthenticated or insufficiently authenticated users to access or modify ad management functions that should require proper capability checks. The CVSS 9.8 indicates this can be exploited without authentication and leads to complete compromise of the ad management functionality.
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
AdfoxlyWordPress extension
<= 1.8.5CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Check AdFoxly plugin versionIn WordPress admin, go to Plugins > Installed Plugins and locate AdFoxly (or Wpfoxly Adfoxly). Check the Version column. Alternatively, open wp-content/plugins/adfoxly/adfoxly.php and look for the 'Version:' header in the plugin comments, or run 'wp plugin list --format=table' via WP-CLI.Affected if Version displayed is 1.8.5 or lower (for example, 1.8.5, 1.8.4, 1.8.0, etc.)
-
Confirm AdFoxly plugin is activeVerify the plugin shows as 'Active' on the WordPress Plugins page, or run 'wp plugin status adfoxly' via WP-CLI to confirm the active status.Affected if Plugin is active on the site (an inactive plugin cannot be exploited)
-
Check for unauthenticated API accessAttempt to access the AdFoxly REST API endpoints without logging in. Make a GET request to /wp-json/adfoxly/v1/ or /wp-json/adfoxly/ads or check if the admin-ajax.php?action=adfoxly_... endpoints respond to unauthenticated requests using a tool like curl or Burp Suite.Affected if The endpoints return valid JSON responses or modify data without requiring WordPress login (a 401/403 error means the check is passing)
A user is affected if the AdFoxly plugin version is 1.8.5 or lower AND the plugin is active, since the missing authorization vulnerability allows unauthenticated access to ad management functions in those versions.
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 AdFoxly plugin to version 1.8.6 or later which includes proper authorization checks. If immediate update is not possible, restrict access to the /wp-admin/ and wp-json/adfoxly endpoints via server-level access controls until the patch can be applied.
Fix this in Adfoxly
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34802 — 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-34802 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