# CVE-2026-42733: WordPress WPCS plugin <= 1.3.1 - Cross Site Scripting (XSS) vulnerability

> An attacker can execute arbitrary scripts in the victim's browser via DOM-based XSS in the WPCS currency-switcher plugin.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L`)
- **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:** 27 May 2026
- **Updated:** 27 May 2026
- **Also known as:** GHSA-5fwp-297j-vmx7

## What is CVE-2026-42733?

CVE-2026-42733 is a high-severity cross-site scripting vulnerability in RealMag777 WPCS, published on 27 May 2026. 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

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in RealMag777 WPCS currency-switcher allows DOM-Based XSS.This issue affects WPCS: from n/a through <= 1.3.1.

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

## Which versions are affected by CVE-2026-42733?


## How do I fix CVE-2026-42733?

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

## Is CVE-2026-42733 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-42733 and fix it if it is affected.

What it is: CVE-2026-42733 is a high-severity cross-site scripting vulnerability in RealMag777 WPCS, published on 27 May 2026. 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-2026-42733 in the wild and no public exploit code.

Affected product: RealMag777 WPCS. 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-2026-42733/ (Markdown: https://insights.sbomify.com/CVE-2026-42733/index.md)
```

## Sources

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

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