Dh Anti AdblockerWordPress extension · Dh Anti Adblocker Project
CVE-2022-47162
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Dannie Herdyawan DH – Anti AdBlocker plugin <= 36 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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the DH – Anti AdBlocker WordPress plugin versions 36 and below allows attackers to trick authenticated administrators into performing unintended actions (such as modifying plugin settings) by forging malicious requests, due to missing or insufficient anti-CSRF token validation on state-changing operations.
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
Dh Anti AdblockerWordPress extension
<= 36CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Verify DH Anti Adblocker plugin is installedLog into WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'DH Anti Adblocker' in the list of active or installed plugins.Affected if The plugin appears in the installed plugins list, regardless of activation status.
-
Check installed plugin versionIn the Plugins list, locate the DH Anti Adblocker plugin entry and note the version number displayed beneath the plugin name. Alternatively, inspect the plugin main file header in wp-content/plugins/dh-anti-adblocker/ for the 'Version' comment tag.Affected if The version number is 36 or lower (e.g., 36, 35, 34, etc.).
-
Inspect plugin for anti-CSRF nonce implementationAccess the plugin source files via FTP or file manager. Examine the main plugin PHP file and any files handling form submissions or AJAX actions. Search for presence of wp_nonce_field, wp_nonce_url, check_admin_referer, or wp_verify_nonce function calls on state-changing operations (settings saves, option updates).Affected if No nonce verification functions are found in files handling POST/GET requests that modify plugin settings or state.
-
Identify state-changing actions without referer validationReview the plugin PHP files for action handlers that modify data (such as update_option, add_option, or database writes). Check if these handlers validate the HTTP Referer or Origin header before processing the request.Affected if State-changing actions lack both nonce tokens AND referer/origin header validation.
You are affected if the DH Anti Adblocker plugin is installed with version 36 or lower AND the plugin lacks nonce verification or referer validation on its settings/save functions.
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 dataUpgrade the DH – Anti AdBlocker plugin to the latest version (>36) which includes proper nonce validation, or implement anti-CSRF tokens (wp_nonce_field) and referer/origin header verification for all form submissions and AJAX actions in the plugin.
Fix this in Dh Anti Adblocker
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-2022-47162 — 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-2022-47162 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