CVE-2022-1166

Noo JobMonster <= 4.6.6 - Sensitive Information Disclosure via Directory Listing

2020-09-11 00:00
Daniel Ruf

Strategic Overview

Status
Patched in 4.6.6.1
Affected Theme
Noo JobMonster
Affected Version
<= 4.6.6
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2022-1166
View all Noo JobMonster vulnerabilities

At a glance

CVE-2022-1166 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Noo JobMonster WordPress theme, affecting versions <= 4.6.6. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.6.6.1; sites on affected versions should update now. Disclosed September 2020, reported by Daniel Ruf.

Vulnerability Overview

The Noo JobMonster theme is vulnerable to Sensitive Information Disclosure via Directory Listing in the /wp-content/uploads/jobmonster/ folder, as it did not include a default PHP file, or .htaccess file in versions up to, and including 4.6.6. This could expose personal data such as people's resumes. Although Directory Listing can be prevented by securely configuring the web server, vendors can also take measures to make it less likely to happen.

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, and no interaction from a victim user.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in Noo JobMonster <= 4.6.6 takes a caller who can reach the endpoint. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Noo JobMonster the fix is 4.6.6.1: builds <= 4.6.6 are affected, anything from 4.6.6.1 onward is not.

Remediation

Update to version 4.6.6.1, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Noo JobMonster 4.6.6.1 closes this, and updating the theme is the step that ends it.

  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-1166https://www.wordfence.com/threat-intel/vulnerabilities/id/07eec594-6c46-4df0-92f1-f090e510d79dhttps://nvd.nist.gov/vuln/detail/CVE-2022-1166

Related records

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