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

CVE-2025-23977

HIGH · 7.1 CVSS v3.1 Published 2025-01-31
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 Bhaskar Dhote Post Carousel Slider post-carousel-slider allows Stored XSS.This issue affects Post Carousel Slider: from n/a through <= 2.0.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

A CSRF vulnerability in the Post Carousel Slider plugin (versions <= 2.0.1) allows authenticated administrators to be tricked into submitting malicious requests that inject persistent JavaScript payloads into carousel content, resulting in stored XSS that executes when other users view the affected carousels.

MitigationUpdate to a patched version of the plugin once released; apply WordPress nonces and capability checks to all admin-side form submissions and AJAX actions to prevent CSRF-based injection.

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 Post Carousel Slider plugin is installed
    Navigate to WordPress admin Plugins page and locate 'Post Carousel Slider' in the list of installed plugins
    Affected if Plugin is present in the WordPress installation
  2. Determine installed plugin version
    Click on the plugin in the WordPress admin Plugins page to view the version number displayed, or inspect the plugin header in the main plugin file
    Affected if Version number is 2.0.1 or lower
  3. Verify admin access to carousel management
    Check if you have administrator role access and can navigate to the plugin settings or carousel creation/edit interface in WordPress admin
    Affected if You can access the plugin admin interface as an authenticated administrator
  4. Inspect carousel content for injected scripts
    Navigate to the plugin admin area where carousels are listed or edited; examine each carousel entry for unexpected script tags, javascript: URLs, onload/onerror attributes, or encoded content that may decode to JavaScript
    Affected if Any carousel entry contains persistent JavaScript code that was not intentionally added by your admin team
  5. Test carousel frontend rendering for XSS execution
    View the public-facing carousels on the site and inspect page source or use browser developer tools to see if unsanitized user-controlled content is being rendered as executable JavaScript
    Affected if Carousel content renders and executes JavaScript in a user's browser without proper sanitization

Your environment is affected if the Post Carousel Slider plugin is installed at version 2.0.1 or lower AND you can access its admin area as an authenticated administrator, regardless of whether you have confirmed actual malicious carousel entries.

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

Update to a patched version of the plugin once released; apply WordPress nonces and capability checks to all admin-side form submissions and AJAX actions to prevent CSRF-based injection.

Recommended fix Moderate confidence

Update to the latest available version of Post Carousel Slider (newer than 2.0.1)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate 'Post Carousel Slider' by Bhaskar Dhote
  4. 4. Check if an update is available for this plugin
  5. 5. If an update is available, update to the latest version which should contain the fix for CVE-2025-23977
  6. 6. Verify the plugin is updated to a version newer than 2.0.1

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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