# CVE-2018-20838: Cross-site scripting in n/a

> Stored XSS in AMP for WP plugin allows attackers to inject malicious scripts into WordPress sites, potentially compromising user sessions.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 May 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-x6fh-2jjp-6486

## What is CVE-2018-20838?

CVE-2018-20838 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 May 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

ampforwp_save_steps_data in the AMP for WP plugin before 0.9.97.21 for WordPress allows stored XSS.

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

## Which versions are affected by CVE-2018-20838?

It affects 1 product.


Products: Magazine3 Amp for Wp.

## How do I fix CVE-2018-20838?

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

## Is CVE-2018-20838 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-48321](https://insights.sbomify.com/CVE-2023-48321/): WordPress Accelerated Mobile Pages Plugin <= 1.0.88.1 is vulnerable to Cross Site Scripting (XSS) (medium 6.5)
- [CVE-2023-6782](https://insights.sbomify.com/CVE-2023-6782/): AMP for WP – Accelerated Mobile Pages <= 1.0.92 - Authenticated (Contributor+) Cross-Site Scripting via Shortcode (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-20838 and fix it if it is affected.

What it is: CVE-2018-20838 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 May 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-20838 in the wild and no public exploit code.

Affected product: n/a. 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-2018-20838/ (Markdown: https://insights.sbomify.com/CVE-2018-20838/index.md)
```

## Sources

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

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