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

CVE-2025-59572

HIGH · 8.8 CVSS v3.1 Published 2025-09-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 purethemes WorkScout-Core workscout-core allows Cross Site Request Forgery.This issue affects WorkScout-Core: from n/a through < 1.7.06.

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

CSRF vulnerability in WorkScout-Core theme allows attackers to induce authenticated users to perform unintended state-changing actions (such as modifying job listings, user settings, or administrative configurations) by tricking them into visiting malicious pages. The absence of anti-CSRF tokens on sensitive endpoints enables attackers to forge requests on behalf of legitimate users.

MitigationImplement anti-CSRF tokens (nonces) on all state-changing operations (POST/PUT/DELETE requests), validate Origin/Referer headers server-side, and set SameSite attribute on session cookies.

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
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. Identify WorkScout-Core theme and version
    Locate the theme's main style.css or functions.php file and read the version declaration, or query your WordPress installation's theme list via wp-cli: wp theme list --status=active
    Affected if The installed version falls within the affected version range or cannot be determined (unknown versions should be treated as potentially vulnerable)
  2. Locate state-changing endpoints in the theme
    Search the theme's PHP files for form handlers processing POST, PUT, or DELETE requests related to job listings, user settings, or admin configurations. Look for files in directories such as /inc/, /includes/, or /classes/ containing functions that modify database records
    Affected if Endpoints that accept state-changing requests without requiring authentication tokens are found
  3. Inspect forms for anti-CSRF tokens
    Examine the theme's form templates (often in /templates/ or /partials/ directories) and their associated PHP handlers. Search for nonce verification functions like wp_verify_nonce, check_ajax_referer, or custom token validation logic
    Affected if Forms that perform job listing modifications, user profile updates, or administrative actions lack nonce/token fields and server-side verification
  4. Verify session cookie configuration
    Check the theme's initialization files or WordPress cookie settings for session cookie definitions. Inspect HTTP response headers from the site using browser dev tools or curl -I to observe the Set-Cookie attributes
    Affected if Session cookies lack the SameSite attribute or have it set to None without Secure flag
  5. Test for Referer/Origin header validation
    Review the PHP handler files for state-changing operations to see if they validate HTTP_REFERER or Origin headers before processing requests
    Affected if No server-side validation of Referer or Origin headers is performed on sensitive POST requests

Your environment is affected if the WorkScout-Core theme is installed and its sensitive endpoints (job listing edits, user settings, admin actions) lack anti-CSRF token verification on state-changing operations.

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 (POST/PUT/DELETE requests), validate Origin/Referer headers server-side, and set SameSite attribute on session cookies.

Recommended fix Moderate confidence

WorkScout-Core version 1.7.06

  1. Backup your WordPress site before making any changes
  2. Update WorkScout-Core plugin to version 1.7.06 or later
  3. Verify the update was successful by checking the installed version number in Plugins > Installed Plugins
  4. Test critical site functionality to ensure the update did not break any features

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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