CVE-2023-31087

JS Job Manager <= 2.0.0 - Cross-Site Request Forgery via multiple functions

2023-06-02 00:00
Yuki Haruma

Strategic Overview

Status
Patched in 2.0.1
Affected Plugin
JS Job Manager
Affected Version
<= 2.0.0
CVSS
5.4Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-31087
View all JS Job Manager vulnerabilities

At a glance

CVE-2023-31087 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the JS Job Manager WordPress plugin, affecting versions <= 2.0.0. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.0.1; sites on affected versions should update now. Disclosed June 2023, reported by Yuki Haruma.

Vulnerability Overview

The JS Job Manager plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.0.0. This is due to missing or incorrect nonce validation on a large number of functions in the plugin. This makes it possible for unauthenticated attackers to make use of nearly all the administrative functionality of the plugin via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in JS Job Manager <= 2.0.0 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For JS Job Manager the fix is 2.0.1: builds <= 2.0.0 are affected, anything from 2.0.1 onward is not.

Remediation

Update to version 2.0.1, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to JS Job Manager: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: JS Job Manager 2.0.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C