dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-46512

HIGH · 7.1 CVSS v3.1 Published 2025-04-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 Shamim Hasan Custom Functions Plugin custom-functions allows Stored XSS.This issue affects Custom Functions Plugin: from n/a through <= 1.1.

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

The Shamim Hasan Custom Functions Plugin versions through 1.1 contains a CSRF vulnerability that allows attackers to inject malicious scripts (Stored XSS). An attacker can craft a malicious link or form that, when clicked by an authenticated administrator, will cause the browser to perform unintended actions that store XSS payloads within the plugin's settings or functionality.

MitigationImplement proper nonces/CSRF tokens on all plugin forms and AJAX actions to verify request origin, and sanitize all user-supplied input before storing or displaying it. Update to a patched version when available.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

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 Shamim Hasan Custom Functions Plugin
    Check your WordPress plugins directory at /wp-content/plugins/ for a folder named 'shamim-hasan-custom-functions' or similar. Alternatively, log into the WordPress admin panel and navigate to Plugins > Installed Plugins to search for 'Shamim Hasan Custom Functions'.
    Affected if The plugin is installed in the plugins directory or appears in the WordPress admin plugin list.
  2. Determine the installed plugin version
    In the WordPress admin under Plugins > Installed Plugins, find the plugin and read the version number from the plugin description. Alternatively, open the main plugin PHP file (usually named plugin-name.php in the plugin folder) and look for the 'Version' header in the plugin comment block at the top of the file.
    Affected if The version is 1.1 or lower (the vulnerability affects all versions through 1.1).
  3. Verify the plugin is active
    In the WordPress admin under Plugins > Installed Plugins, confirm the plugin shows as 'Active'. The vulnerability requires the plugin to be enabled for an attacker to trigger the CSRF and store XSS payloads.
    Affected if The plugin is active on the site.
  4. Inspect plugin settings for stored XSS payloads
    Navigate to any settings pages provided by this plugin (typically under Settings or a dedicated menu item created by the plugin). Inspect page source or view the rendered HTML to look for unsanitized script tags, iframe elements, or event handlers (onerror, onload, onclick) in input fields. Also check the WordPress database wp_options table for any entries with option_name containing the plugin identifier that contain suspicious JavaScript code.
    Affected if Any stored XSS payloads are found in plugin settings pages or in the WordPress database options table related to this plugin.
  5. Review plugin source code for missing CSRF protection
    If you have file access, examine the main plugin PHP file(s) for form handlers and AJAX actions. Search for the presence of 'wp_nonce' or 'check_admin_referer' function calls. The absence of these nonce verification functions in forms that handle admin actions indicates the CSRF vulnerability exists.
    Affected if Forms or AJAX handlers in the plugin code lack nonce verification (wp_nonce_field, wp_nonce_url, or check_admin_referer are not present).

Your environment is affected if the Shamim Hasan Custom Functions Plugin versions 1.1 or lower is installed and active, especially if you find forms lacking CSRF tokens or discover stored XSS payloads in plugin settings or the database.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper nonces/CSRF tokens on all plugin forms and AJAX actions to verify request origin, and sanitize all user-supplied input before storing or displaying it. Update to a patched version when available.

Have this fixed 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 help mitigating

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-2025-46512 — 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-2025-46512 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