CVE-2026-57786
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in purethemes WorkScout-Core workscout-core allows Authentication Bypass.This issue affects WorkScout-Core: from n/a through <= 1.7.08.
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 confidenceA Cross-Site Request Forgery (CSRF) vulnerability in the WorkScout-Core WordPress theme/plugin allows attackers to bypass authentication mechanisms. By tricking authenticated users into visiting malicious pages, attackers can potentially execute unauthorized actions on behalf of the victim, including administrative operations.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm WorkScout-Core installationCheck your WordPress installation for the WorkScout-Core plugin or theme files in wp-content/plugins/ or wp-content/themes/ directory, or look for it in the WordPress admin under Plugins.Affected if WorkScout-Core is not present in the installation
-
Determine installed versionIf the plugin/theme is installed, locate its main PHP file (often similar to workscout-core.php) and look for a version comment or constant at the top of the file, or check the version field in the WordPress plugins admin page.Affected if The installed version falls within the affected range (any version lacking CSRF protection)
-
Inspect form submissions for nonce tokensExamine the plugin PHP files for form handling code. Search for state-changing forms (POST requests) and verify they include wp_nonce_field() or similar nonce generation functions.Affected if Forms that perform actions lack nonce validation tokens
-
Verify AJAX action protectionSearch the plugin files for add_action('wp_ajax_') calls and verify each AJAX handler includes check_admin_referer() or wp_verify_nonce() before processing requests.Affected if AJAX endpoints lack nonce verification
-
Check cookie configurationInspect the plugin code for setcookie() calls and verify SameSite and Secure attributes are set on authentication-related cookies.Affected if Cookies are set without SameSite=Strict or SameSite=Lax attributes
If WorkScout-Core is installed and any of its forms or AJAX actions lack nonce verification, the site is vulnerable to CVE-2026-57786.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement anti-CSRF tokens (nonces) on all state-changing form submissions and AJAX actions within the plugin. Additionally, add SameSite cookie attributes and implement proper referrer validation.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57786 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-57786 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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