# CVE-2022-1166: JobMonster < 4.6.6.1 - Directory Listing in Upload Folder

> An attacker can list files in the upload directory to expose personal data like resumes due to missing directory protection files.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Apr 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-952h-ff56-x6g3

## What is CVE-2022-1166?

CVE-2022-1166 is a medium-severity vulnerability in Unknown Noo JobMonster, published on 4 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The JobMonster Theme was vulnerable to Directory Listing in the /wp-content/uploads/jobmonster/ folder, as it did not include a default PHP file, or .htaccess file. 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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2022-1166?

It affects 1 product.


Products: Nootheme Jobmonster.

## How do I fix CVE-2022-1166?

No fix has been published for CVE-2022-1166 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-1166 being exploited?

There is no known exploitation of CVE-2022-1166 in the wild and no public exploit code.

## Other vulnerabilities in Unknown Noo JobMonster

- [CVE-2022-1170](https://insights.sbomify.com/CVE-2022-1170/): JobMonster < 4.5.2.9 - Unauthenticated Reflected Cross-Site Scripting (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-1166 and fix it if it is affected.

What it is: CVE-2022-1166 is a medium-severity vulnerability in Unknown Noo JobMonster, published on 4 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-1166 in the wild and no public exploit code.

Affected product: Unknown Noo JobMonster. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-1166/ (Markdown: https://insights.sbomify.com/CVE-2022-1166/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-1166
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-1166
- OSV: https://osv.dev/vulnerability/CVE-2022-1166

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-1166/
Summaries are generated and may contain mistakes; the official description above is the record.