CVE-2026-57786
Deferred Deferred - Pending Action

Cross-Site Request Forgery in WorkScout-Core

Vulnerability report for CVE-2026-57786, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-13

Last updated on: 2026-07-13

Assigner: Patchstack

Description

Cross-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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-13
Last Modified
2026-07-13
Generated
2026-08-02
AI Q&A
2026-07-13
EPSS Evaluated
2026-08-01
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
purethemes workscout-core to 1.7.08 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-352 The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a Cross-Site Request Forgery (CSRF) issue in the WordPress WorkScout-Core Plugin versions 1.7.08 and below.

CSRF allows an attacker to trick a privileged user into performing unwanted actions, such as clicking a malicious link or submitting a form, which can lead to authentication bypass.

The vulnerability requires user interaction and affects authentication mechanisms, potentially allowing unauthorized access.

Detection Guidance

Detecting a Cross-Site Request Forgery (CSRF) vulnerability like CVE-2026-57786 in the WorkScout-Core plugin on your system or network involves checking for the presence of the vulnerable plugin version and monitoring for suspicious activity. Below are some methods and commands to help identify the vulnerability.

  • Check the installed version of the WorkScout-Core plugin on your WordPress site. Navigate to the WordPress admin dashboard, go to 'Plugins', and look for WorkScout-Core. If the version is 1.7.08 or below, the site is vulnerable.
  • Use the WordPress command-line interface (WP-CLI) to check the plugin version. Run the following command: wp plugin list --name=workscout-core --fields=name,version,status
  • Inspect the plugin files directly on the server. Navigate to the WordPress plugins directory (typically /wp-content/plugins/) and check the version in the workscout-core plugin's readme.txt or main plugin file.
  • Monitor network traffic for unusual or unexpected requests to the WorkScout-Core plugin endpoints. Tools like Wireshark, Burp Suite, or network firewalls can help detect suspicious activity, such as unauthorized form submissions or state-changing requests without proper CSRF tokens.
  • Review server logs for unexpected POST requests or actions performed by privileged users without their knowledge. Look for patterns that indicate CSRF exploitation attempts, such as repeated requests to sensitive endpoints.
  • Use a vulnerability scanner like WPScan to detect the presence of the vulnerable plugin version. Run the following command: wpscan --url your-wordpress-site --enumerate vp --plugins-detection aggressive

Since there is no official patch available, immediate action is recommended, such as disabling the plugin or seeking assistance from a web developer to implement custom mitigations.

Impact Analysis

Exploitation of this vulnerability can lead to authentication bypass, meaning an attacker could gain unauthorized access to the affected system.

This can result in full compromise of confidentiality, integrity, and availability of the system, as indicated by the high CVSS score of 8.8.

However, exploitation requires a privileged user to perform an action such as clicking a malicious link, which lowers the likelihood but does not eliminate the risk.

Compliance Impact

A Cross-Site Request Forgery (CSRF) vulnerability in WorkScout-Core that allows authentication bypass can have significant implications for compliance with standards and regulations like GDPR and HIPAA.

  • GDPR: The vulnerability could lead to unauthorized access to sensitive personal data, violating GDPR's requirements for data protection and user consent. Under GDPR, organizations must implement appropriate technical measures to ensure data security, and a CSRF vulnerability that allows authentication bypass may be seen as a failure to meet these obligations.
  • HIPAA: If the affected system processes or stores protected health information (PHI), this vulnerability could result in unauthorized access to PHI, violating HIPAA's Security Rule. The rule mandates safeguards to protect the confidentiality, integrity, and availability of electronic PHI, and a CSRF flaw that enables authentication bypass may constitute a breach of these requirements.

Additionally, the high CVSS score (8.8) indicates a severe risk, which may trigger mandatory breach notifications under GDPR or HIPAA if exploitation leads to unauthorized data access or disclosure.

Mitigation Strategies

Immediate action is recommended to update the affected WorkScout-Core plugin to a non-vulnerable version if available.

If no official patch is available, users should seek assistance from their hosting provider or web developer to implement mitigation strategies.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-57786. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart