AdfoxlyWordPress extension · Wpfoxly
CVE-2023-30754
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 · uneditedUnauth. Reflected Cross-Site Scripting (XSS) vulnerability in AdFoxly AdFoxly – Ad Manager, AdSense Ads & Ads.Txt plugin <= 1.8.5 versions.
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 confidenceAn unauthenticated reflected cross-site scripting (XSS) vulnerability exists in the AdFoxly WordPress advertising plugin versions 1.8.5 and below. Attackers can inject malicious JavaScript into vulnerable parameters that are reflected back in HTTP responses without proper sanitization or output encoding.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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.
-
Confirm AdFoxly plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'AdFoxly' or 'Wpfoxly Adfoxly' in the list of active pluginsAffected if AdFoxly plugin appears in the installed plugins list
-
Identify the installed AdFoxly versionIn WordPress admin, go to Plugins > Installed Plugins, find AdFoxly, and note the version number displayed below the plugin nameAffected if The version listed is 1.8.5 or lower
-
Verify the plugin is activeIn Plugins > Installed Plugins, check if AdFoxly shows as 'Active' under the plugin status columnAffected if The plugin is active and the version is 1.8.5 or below
-
Check for reflected parameters in HTTP requestsIf you have access to server logs or traffic capture, examine HTTP requests to your WordPress site for query parameters that might be reflected in the response without encoding. Common XSS vectors in ad plugins include parameters like 'banner_id', 'ad_id', 'zone', or 'url' parameters.Affected if Unsanitized user input from request parameters appears reflected in the HTML response
You are affected if AdFoxly plugin version 1.8.5 or lower is installed and active on your WordPress site, making reflected parameters vulnerable to XSS injection.
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 a version beyond 1.8.5 which contains the security patch. If immediate patching is not possible, implement web application firewall (WAF) rules to filter malicious XSS payloads in requests to affected endpoints.
Fix this in Adfoxly
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30754 — 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-2023-30754 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