dbcve.org
Custom CursorsWordPress extension · Hamidrezasepehr

CVE-2023-32739

HIGH · 8.8 CVSS v3.1 Published 2023-11-09
Fix available
A fix is available. Upgrade to 3.2 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 Web_Trendy WP Custom Cursors | WordPress Cursor Plugin plugin < 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

A Cross-Site Request Forgery (CSRF) vulnerability in the Web_Trendy WP Custom Cursors WordPress plugin versions before 3.2 allows attackers to trick authenticated administrators into performing unintended actions, such as modifying cursor settings or plugin configuration, by exploiting the absence of anti-CSRF tokens on state-changing requests.

MitigationUpgrade the plugin to version 3.2 or later. For immediate mitigation, ensure admin sessions are not left unattended and consider implementing additional CSRF protections at the web server level (e.g., verifying Origin/Referer headers) until the plugin is updated.

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
Custom CursorsWordPress extension
Affected:< 3.2

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. Confirm the plugin is installed
    Check your WordPress plugins directory (wp-content/plugins) for a folder containing 'custom-cursors', 'hamidrezasepehr', or 'web-trendy-cursors' in the name. Alternatively, log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins to locate the plugin listed as 'Custom Cursors' or 'Hamidrezasepehr Custom Cursors'.
    Affected if The plugin folder or entry exists in the WordPress plugins directory or admin plugin list
  2. Determine the installed version
    In the WordPress admin, find the plugin in Plugins > Installed Plugins and look for the version number displayed below the plugin name. Alternatively, open the main plugin PHP file (usually named index.php or the plugin folder name) and locate the 'Version' header in the plugin comment block at the top.
    Affected if The version shown is lower than 3.2 (for example, 3.1, 3.0, 2.x, or any version number less than 3.2)
  3. Verify admin access to plugin settings
    Log in as an administrator and navigate to the plugin settings page (typically found under Settings or a dedicated Custom Cursors menu item in the left sidebar). Attempt to locate any configuration options for cursors, such as adding/editing custom cursors, changing cursor sets, or modifying plugin behavior settings.
    Affected if You can access and modify cursor-related settings through the WordPress admin interface while logged in as an administrator

You are affected if the Hamidrezasepehr Custom Cursors plugin is installed with any version lower than 3.2 and you have administrator access to modify its settings.

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.2 or later
Fixed in 3.2
Interim mitigation

Upgrade the plugin to version 3.2 or later. For immediate mitigation, ensure admin sessions are not left unattended and consider implementing additional CSRF protections at the web server level (e.g., verifying Origin/Referer headers) until the plugin is updated.

Recommended fix High confidence

Custom Cursors plugin version 3.2 or later

  1. 1. Create a complete backup of the WordPress site, including database and files
  2. 2. Navigate to the WordPress admin dashboard under Plugins > Installed Plugins
  3. 3. Locate the 'Custom Cursors' (or 'WP Custom Cursors | WordPress Cursor Plugin') plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to version 3.2 or later
  5. 5. Alternatively, download version 3.2 or latest from the official WordPress plugin repository and upload manually
  6. 6. After updating, clear any site caching if applicable
  7. 7. Verify the plugin is functioning correctly by testing cursor functionality on the site
  8. 8. Confirm the updated version number displays correctly in the Plugins list

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

Fix this in Custom Cursors 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-32739 — 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-32739 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