dbcve.org
Top 10WordPress extension · Webberzone

CVE-2023-47238

HIGH · 8.8 CVSS v3.1 Published 2023-11-09
Fix available
A fix is available. Upgrade to 3.3.3 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in WebberZone Top 10 – WordPress Popular posts by WebberZone plugin <= 3.3.2 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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the WebberZone Top 10 WordPress plugin affecting versions 3.3.2 and below. The vulnerability allows attackers to trick authenticated administrators into performing unintended actions such as modifying plugin settings or injecting malicious content through forged requests.

MitigationUpdate the WebberZone Top 10 plugin to the latest version which implements anti-CSRF tokens (nonces) and proper referer validation on all state-changing operations. If no update is available, disable the plugin until a patch is released.

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
Top 10WordPress extension
Affected:< 3.3.3

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

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

  1. Locate the WebberZone Top 10 plugin installation
    Access your WordPress site via FTP or file manager and navigate to /wp-content/plugins/top-10/ directory, or check via WordPress admin under Plugins > Installed Plugins
    Affected if The plugin directory exists and the plugin is listed in your WordPress installation
  2. Identify the installed version number
    Open the main plugin file (typically top-10.php) and locate the version string in the plugin header comment, or check the version displayed in the WordPress admin plugins list
    Affected if The version displayed is 3.3.2 or lower (any version below 3.3.3)
  3. Confirm the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify that WebberZone Top 10 shows as Active
    Affected if The plugin is active and running on versions below 3.3.3
  4. Check for admin authentication presence
    Review your WordPress user roles and confirm administrator accounts exist and have access to the plugin settings
    Affected if Administrator accounts are present and the vulnerable plugin version is active, making CSRF attacks possible against admin sessions

You are affected if the WebberZone Top 10 plugin is installed and active at version 3.3.2 or below, as this version lacks anti-CSRF token protection on state-changing operations.

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
Upgrade available Upgrade to 3.3.3 or later
Fixed in 3.3.3
Interim mitigation

Update the WebberZone Top 10 plugin to the latest version which implements anti-CSRF tokens (nonces) and proper referer validation on all state-changing operations. If no update is available, disable the plugin until a patch is released.

Recommended fix High confidence

Version 3.3.3 or later

  1. Backup your WordPress site database and files
  2. Navigate to WordPress admin dashboard > Plugins
  3. Find 'WebberZone Top 10 – WordPress Popular posts' plugin
  4. Click 'Update now' to upgrade to version 3.3.3 or later
  5. Verify the plugin version after update by checking the installed plugins list
  6. Test that the popular posts functionality works correctly

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

Fix this in Top 10 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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