# CVE-2018-11522: Yosoro 1.0.4 has stored XSS.


- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 1 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** CVE-2018-1000530, GHSA-r2wj-gwxx-6mf5

## What is CVE-2018-11522?

CVE-2018-11522 is a medium-severity vulnerability in n/a, published on 1 Jun 2018. 

### Official description

Yosoro 1.0.4 has stored XSS.

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

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

It affects 1 product.


Products: Yosoro Project Yosoro.

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

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

## Is CVE-2018-11522 being exploited?

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

Public exploit code:

- Yosoro 1.0.4 - Remote Code Execution (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-11522 is a medium-severity vulnerability in n/a, published on 1 Jun 2018. 
Exploitation: There is no known exploitation of CVE-2018-11522 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-11522/ (Markdown: https://insights.sbomify.com/CVE-2018-11522/index.md)
```

## Sources

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

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