dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-36509

MEDIUM · 5.4 CVSS v3.1 Published 2024-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Missing Authorization vulnerability in Suresh Chand CHP Ads Block Detector allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects CHP Ads Block Detector: from n/a through 3.9.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 confidence

The CHP Ads Block Detector WordPress plugin versions up to 3.9.5 contains a missing authorization vulnerability that allows exploitation of incorrectly configured access control security levels. An attacker with low privileges could potentially bypass intended access restrictions to access functionality or data they should not have permission to view or modify.

MitigationUpdate to the latest version of the plugin (3.9.6 or later) which contains proper authorization controls. If no patched version exists, implement role-based capability checks at all admin AJAX endpoints and sensitive functions within the plugin.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify CHP Ads Block Detector plugin is installed
    Check for the plugin directory at wp-content/plugins/chp-ads-block-detector/ or look for the plugin in WordPress admin under Plugins > Installed Plugins
    Affected if The plugin directory exists in the WordPress plugins folder or the plugin appears in the WordPress admin plugin list
  2. Determine the installed plugin version
    Open the main plugin file (chp-ads-block-detector.php) and locate the Version header in the plugin comment block at the top, or check the readme.txt file
    Affected if The version number shown is 3.9.5 or lower (for example: 3.9.0, 3.8.2, 3.5, etc.)
  3. Check for vulnerable AJAX endpoints
    Examine the plugin PHP files for admin-ajax.php action hooks (add_action('wp_ajax_...')) and verify if they include current_user_can() or capability checks before executing sensitive operations
    Affected if AJAX action handlers exist without current_user_can() validation or other authorization checks on functions that modify settings or access sensitive data
  4. Identify sensitive function accessibility
    Review the plugin code for functions that handle plugin settings, user data, or configuration changes and determine if they can be called by low-privilege users (subscriber, contributor role) without authentication
    Affected if Sensitive functions (settings save, data export, configuration changes) are callable by any authenticated user regardless of role

A user is affected if the CHP Ads Block Detector plugin version 3.9.5 or lower is installed and the vulnerable authorization checks are present in the code.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of the plugin (3.9.6 or later) which contains proper authorization controls. If no patched version exists, implement role-based capability checks at all admin AJAX endpoints and sensitive functions within the plugin.

Recommended fix Moderate confidence

Latest version of CHP Ads Block Detector (version > 3.9.5)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate CHP Ads Block Detector plugin
  4. Check if an update is available and upgrade to the latest version
  5. Verify the plugin was updated to a version higher than 3.9.5

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-36509 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-36509 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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