# CVE-2022-1567: WP JS <= 2.0.6 - Reflected Cross-Site Scripting

> Attackers can execute arbitrary scripts in admin sessions via unvalidated input in the WP JS plugin.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 May 2022
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-f2g6-m663-wjp3

## What is CVE-2022-1567?

CVE-2022-1567 is a medium-severity cross-site scripting vulnerability in halmat WP JS, published on 10 May 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The WP-JS plugin for WordPress contains a script called wp-js.php with the function wp_js_admin, that accepts unvalidated user input and echoes it back to the user. This can be used for reflected Cross-Site Scripting in versions up to, and including, 2.0.6.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Wp-Js Project Wp-Js.

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

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

## Is CVE-2022-1567 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-1567 is a medium-severity cross-site scripting vulnerability in halmat WP JS, published on 10 May 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-1567 in the wild and no public exploit code.

Affected product: halmat WP JS. 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-1567/ (Markdown: https://insights.sbomify.com/CVE-2022-1567/index.md)
```

## Sources

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

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