dbcve.org
UserbackWordPress extension

CVE-2023-46089

HIGH · 8.8 CVSS v3.1 Published 2023-10-22
Fix available
A fix is available. Upgrade to after 1.0.13 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 Lee Le @ Userback Userback plugin <= 1.0.13 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 Userback WordPress plugin allows attackers to trick authenticated users into performing unintended actions by forged requests. The vulnerability exists in versions 1.0.13 and earlier, potentially enabling unauthorized modifications to plugin settings or user actions.

MitigationImplement anti-CSRF tokens (nonces) on all form submissions and AJAX endpoints within the plugin, and validate the nonce server-side before processing any state-changing requests.

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
UserbackWordPress extension
Affected:<= 1.0.13

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 Userback plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Userback' in the list, or check the wp-content/plugins/ directory for a userback folder
    Affected if Userback plugin is installed and active on the WordPress site
  2. Determine the installed version of Userback plugin
    In WordPress admin > Plugins > Installed Plugins, click on the Userback plugin to view its version number, or open wp-content/plugins/userback/readme.txt and check the 'Stable tag' in the header
    Affected if The version number is 1.0.13 or lower
  3. Inspect plugin source code for nonce validation
    Examine the main plugin PHP files (typically userback.php or similar in wp-content/plugins/userback/) and search for wp_verify_nonce(), check_ajax_referer(), or wp_nonce_field() function calls on form handling and AJAX endpoints
    Affected if No nonce verification functions are found in the plugin code handling form submissions or AJAX requests

The environment is affected if the Userback WordPress plugin version is 1.0.13 or earlier and the plugin code lacks proper nonce validation on state-changing requests.

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.

From vendor data
Upgrade available Upgrade to a release after 1.0.13
Interim mitigation

Implement anti-CSRF tokens (nonces) on all form submissions and AJAX endpoints within the plugin, and validate the nonce server-side before processing any state-changing requests.

Fix this in Userback Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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