# CVE-2023-54413: WPML Multilingual CMS WordPress Plugin < 4.6.1 Reflected XSS via wp-login.php wp_lang


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** GHSA-p7q8-6fx6-c54g

## What is CVE-2023-54413?

CVE-2023-54413 is a medium-severity vulnerability in OnTheGoSystems WPML Multilingual CMS, published on 22 Oct 2026. 

### Official description

WPML Multilingual CMS plugin for WordPress before 4.6.1 contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject script by supplying crafted input in the wp_lang parameter. Attackers can lure users to /wp-login.php with a wp_lang value injecting an image input with an obfuscated onfocus handler to execute JavaScript in the victim's browser. Exploitation evidence was first observed by the Shadowserver Foundation on 2025-11-12.

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

## Which versions are affected by CVE-2023-54413?


## How do I fix CVE-2023-54413?

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

## Is CVE-2023-54413 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-54413 and fix it if it is affected.

What it is: CVE-2023-54413 is a medium-severity vulnerability in OnTheGoSystems WPML Multilingual CMS, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2023-54413 in the wild and no public exploit code.

Affected product: OnTheGoSystems WPML Multilingual CMS. 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-2023-54413/ (Markdown: https://insights.sbomify.com/CVE-2023-54413/index.md)
```

## Sources

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

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