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

CVE-2025-32478

HIGH · 7.1 CVSS v3.1 Published 2025-04-09
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 Mario Aguiar WP SexyLightBox wp-sexylightbox allows Stored XSS.This issue affects WP SexyLightBox: from n/a through <= 0.5.3.

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 WP SexyLightBox WordPress plugin allows authenticated or unauthenticated attackers to craft malicious requests that result in Stored XSS. The lack of proper anti-CSRF tokens on form submissions or AJAX endpoints enables attackers to inject malicious scripts that persist on the affected pages.

MitigationImplement anti-CSRF tokens (nonces) on all state-changing operations and ensure all user-supplied data is properly sanitized before output. Until a patch is available, consider disabling the plugin or restricting access to trusted users only.

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. Confirm WP SexyLightBox plugin is installed
    Log in to WordPress admin dashboard, navigate to Plugins > Installed Plugins, and search for 'SexyLightBox' or 'Sexy Light Box' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'sexy-lightbox' or similar.
    Affected if The plugin appears in the installed plugins list and is active.
  2. Identify the installed plugin version
    In the WordPress admin Plugins page, click on the plugin name to view its details, or check the plugin's main PHP file header for the 'Version' comment. Compare this version against any official release notes from the vendor.
    Affected if A version of WP SexyLightBox is installed and active.
  3. Inspect form submissions for missing CSRF tokens
    Using browser developer tools or a proxy (Burp Suite), navigate to any settings or submission forms within the SexyLightBox plugin pages. Inspect the HTML source of forms to check for the presence of 'nonce', '_wpnonce', or 'security' hidden input fields.
    Affected if Form submissions contain no nonce or CSRF token fields, or the submitted data does not trigger a nonce verification check on the server side.
  4. Audit AJAX endpoints for nonce verification
    Examine the plugin's PHP source code, specifically looking for AJAX handlers registered via 'wp_ajax_' and 'wp_ajax_nopriv_' hooks. Check if these handlers call 'check_ajax_referer' or 'wp_verify_nonce' before processing requests.
    Affected if AJAX endpoints exist in the plugin and do not perform nonce verification before processing state-changing requests.
  5. Test for Stored XSS via form injection
    If unauthenticated or low-privileged user access is possible to plugin forms, submit a test payload like '<script>alert(1)</script>' in any text input fields. Then navigate to pages where this data might be displayed to see if the script executes.
    Affected if User-supplied input is rendered on the frontend without proper sanitization and encoding, allowing stored scripts to execute.

If the WP SexyLightBox plugin is installed and any of its forms or AJAX endpoints lack CSRF token verification, the environment is vulnerable to CVE-2025-32478.

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

Implement anti-CSRF tokens (nonces) on all state-changing operations and ensure all user-supplied data is properly sanitized before output. Until a patch is available, consider disabling the plugin or restricting access to trusted users only.

Recommended fix Moderate confidence
  1. 1. Since this plugin (WP SexyLightBox <= 0.5.3) appears to be unmaintained with no available security patch, immediately deactivate and remove the plugin from your WordPress installation.
  2. 2. Search for an actively maintained alternative lightbox plugin in the official WordPress plugin repository that receives regular security updates.
  3. 3. Before installing any replacement, verify the alternative has recent security updates and good review ratings.
  4. 4. If you must continue using this plugin temporarily, implement WordPress CSRF nonces on all form submissions and AJAX actions within the plugin code, though this requires custom code modifications to abandoned software.
Caveat Plugin is abandoned with no known fixed version; replacement with an actively maintained alternative is required

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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