dbcve.org
About Me 3000 WidgetWordPress extension · About Me 3000 Widget Project

CVE-2023-25474

HIGH · 8.8 CVSS v3.1 Published 2023-05-23
Fix available
A fix is available. Upgrade to after 2.2.6 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 Csaba Kissi About Me 3000 widget plugin <= 2.2.6 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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the About Me 3000 widget WordPress plugin (versions 2.2.6 and below) allows attackers to trick authenticated administrators into performing unintended state-changing actions, such as modifying widget settings or plugin configuration, by crafting malicious requests that the victim's browser automatically submits.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) on all forms and state-changing operations within the plugin, and validate the Origin/Referer headers on server-side request handling to ensure requests originate from legitimate sources.

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
About Me 3000 WidgetWordPress extension
Affected:<= 2.2.6

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. Check if About Me 3000 Widget plugin is installed
    Navigate to WordPress admin dashboard > Plugins, or inspect the wp-content/plugins/ directory for a folder named 'about-me-3000-widget' or similar
    Affected if The plugin is present in the installation
  2. Verify the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > locate About Me 3000 Widget and read the version number from the plugin description header
    Affected if Version is 2.2.6 or lower (any version number less than or equal to 2.2.6)
  3. Confirm the plugin is active
    In WordPress admin > Plugins, check if About Me 3000 Widget shows as 'Active' rather than 'Inactive'
    Affected if Plugin is currently activated on the site
  4. Check if settings/configuration forms lack CSRF protection
    Access the plugin settings page (usually under Settings or Appearance > Widgets), view the HTML source of any form elements, and inspect whether hidden anti-CSRF token fields (such as wpnonce or similar) are present in state-changing forms
    Affected if No anti-CSRF token fields are found in forms that modify widget settings or plugin configuration

If the About Me 3000 Widget plugin is installed at version 2.2.6 or below and is active, the site is affected by this CSRF vulnerability.

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 a release after 2.2.6
Interim mitigation

Implement anti-CSRF tokens (synchronizer token pattern) on all forms and state-changing operations within the plugin, and validate the Origin/Referer headers on server-side request handling to ensure requests originate from legitimate sources.

Recommended fix High confidence

Version 2.2.7 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'About Me 3000 Widget' plugin
  4. Click 'Update now' if an update is available, or manually download version 2.2.7 from the WordPress plugin repository and upload it
  5. Verify the updated version is 2.2.7 or higher

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

Fix this in About Me 3000 Widget Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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