CVE-2017-9603

WP Jobs < 1.5 - SQL Injection

2017-06-11 00:00
Dimitrios Tsagkarakis

Strategic Overview

Status
Patched in 1.5
Affected Plugin
WP Jobs
Affected Version
< 1.5
CVSS
8.8High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2017-9603
View all WP Jobs vulnerabilities

At a glance

CVE-2017-9603 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WP Jobs WordPress plugin, affecting versions < 1.5. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 1.5; sites on affected versions should update now. Disclosed June 2017, reported by Dimitrios Tsagkarakis.

Vulnerability Overview

SQL injection vulnerability in the WP Jobs plugin before 1.5 for WordPress allows authenticated users to execute arbitrary SQL commands via the jobid parameter to wp-admin/edit.php.

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 interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Reaching this weakness in WP Jobs < 1.5 takes a caller who can reach the endpoint. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.

A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For WP Jobs the fix is 1.5: builds < 1.5 are affected, anything from 1.5 onward is not.

Remediation

Update to version 1.5, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WP Jobs: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Jobs 1.5 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