dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-23887

MEDIUM · 5.3 CVSS v3.1 Published 2024-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 Shaon Easy Google Analytics for WordPress allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Easy Google Analytics for WordPress: from n/a through 1.6.0.

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

Missing authorization vulnerability in the Easy Google Analytics WordPress plugin allows unauthenticated or unauthorized users to access functionality or data that should be restricted. The 'incorrectly configured access control security levels' indicates certain admin actions, AJAX endpoints, or settings pages can be accessed without proper capability checks or authentication.

MitigationImplement proper authorization checks (such as current_user_can() capability verification) and nonce validation on all sensitive plugin functions, admin pages, and AJAX endpoints to ensure only authorized users can access them.

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
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 checks

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

  1. Confirm plugin installation
    Navigate to WordPress admin dashboard > Plugins and verify the Easy Google Analytics plugin is installed and activated
    Affected if The plugin is installed and active in WordPress
  2. Identify installed version
    In Plugins page, find Easy Google Analytics and note the version number displayed
    Affected if Version matches or falls within any known affected version range for this CVE
  3. Inspect AJAX endpoint authorization
    Examine the plugin's PHP files (typically in wp-content/plugins/easy-google-analytics/) for AJAX handlers - look for wp_ajax_ and wp_ajax_nopriv_ hooks without current_user_can() capability checks before executing sensitive operations
    Affected if AJAX endpoints lack proper authorization checks and are accessible to unauthorized users
  4. Inspect admin page access controls
    Review plugin PHP files for admin menu registrations and page callbacks - verify that admin pages call current_user_can() or similar capability checks before displaying sensitive data or performing settings changes
    Affected if Admin pages or settings panels can be accessed without proper capability verification
  5. Inspect nonce validation
    Search plugin PHP files for form submissions and action handlers - verify that nonce verification (check_admin_referer, wp_verify_nonce, or similar) is present on all sensitive actions
    Affected if Sensitive actions lack nonce validation, allowing potential CSRF attacks

If Easy Google Analytics plugin is active and its code lacks authorization checks on AJAX endpoints, admin pages, or nonce validation on sensitive operations, the environment is affected by this CVE.

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

Implement proper authorization checks (such as current_user_can() capability verification) and nonce validation on all sensitive plugin functions, admin pages, and AJAX endpoints to ensure only authorized users can access them.

Recommended fix Moderate confidence

Latest version of Easy Google Analytics for WordPress (greater than 1.6.0)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Easy Google Analytics for WordPress' in the plugin list
  4. 4. Check if an update is available - if so, update to the latest version
  5. 5. If no update is available through the WordPress admin, download the latest version from the WordPress Plugin Repository and reinstall manually
  6. 6. After updating, verify the plugin is functioning correctly and review any settings that may have been affected

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-23887 — 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-23887 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