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

CVE-2025-12590

MEDIUM · 6.1 CVSS v3.1 Published 2025-11-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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
The YSlider plugin for WordPress is vulnerable to Cross-Site Request Forgery to Stored Cross-Site Scripting in all versions up to, and including, 1.1. This is due to missing nonce verification on the content configuration page and insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages via a forged request granted they can trick an administrator into performing an action such as clicking on a link. The injected scripts will execute whenever a user accesses an injected page.

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 · high confidence

The YSlider WordPress plugin lacks nonce verification on its content configuration page, allowing CSRF attacks. Combined with insufficient input sanitization and missing output escaping, this enables unauthenticated attackers to inject persistent JavaScript payloads via forged requests that trick administrators into clicking malicious links. The injected scripts execute on all pages where the affected slider content is displayed.

MitigationUpdate YSlider to the latest version which implements nonce verification on admin actions and properly sanitizes input/output. Until then, admin users should avoid clicking untrusted links.

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
None

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

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. Verify YSlider plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and locate YSlider in the list, or check the /wp-content/plugins/ directory for the yslider folder
    Affected if The YSlider plugin folder exists in the WordPress plugins directory
  2. Identify installed YSlider version
    In Plugins list, click on YSlider to view plugin details including version number, or read version from the main plugin PHP file header
    Affected if The installed version is older than the version that introduced nonce verification and proper sanitization (compare to latest available version)
  3. Confirm plugin is active
    Check the Plugins list in WordPress admin - the plugin should show as 'Active' under YSlider
    Affected if YSlider is activated and accessible to administrators
  4. Verify admin access to content configuration
    Navigate to YSlider settings in WordPress admin (typically under Settings or a dedicated YSlider menu) and access the content/slider configuration page
    Affected if The content configuration page is accessible without additional security prompts or token verification
  5. Inspect slider content for suspicious script injections
    Review any saved slider content/configurations in the YSlider settings for unexpected script tags, event handlers, or encoded JavaScript payloads in text fields
    Affected if Any slider configuration contains unescaped HTML, script tags, or JavaScript event handlers (onclick, onerror, etc.)

A user is affected if the YSlider plugin is installed, active, and running a version prior to the one that added nonce verification and output escaping, with accessible admin configuration pages.

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 YSlider to the latest version which implements nonce verification on admin actions and properly sanitizes input/output. Until then, admin users should avoid clicking untrusted links.

Recommended fix Moderate confidence

YSlider version greater than 1.1 (check plugins.trac.wordpress.org for the specific fixed release)

  1. Check the WordPress plugin repository for YSlider at plugins.trac.wordpress.org to identify the latest fixed version
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate the YSlider plugin
  4. If the current version is 1.1 or below, click 'Update Now' to upgrade to the fixed version
  5. After updating, verify the plugin is functioning correctly on the site

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

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-12590 — 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-12590 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