# CVE-2021-24618: Donate With QRCode < 1.4.5 - Stored Cross-Site Scripting

> Stored XSS in Donate With QRCode plugin allows attackers to inject scripts via QRCode settings, potentially leading to code execution or session hijacking.

- **Severity:** Medium 5.4 (`CVSS:3.1/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:** 20 Sep 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-3g5v-m9jm-mw8w

## What is CVE-2021-24618?

CVE-2021-24618 is a medium-severity cross-site scripting vulnerability in Unknown Donate With QRCode, published on 20 Sep 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The Donate With QRCode WordPress plugin before 1.4.5 does not sanitise or escape its QRCode Image setting, which result into a Stored Cross-Site Scripting (XSS). Furthermore, the plugin also does not have any CSRF and capability checks in place when saving such setting, allowing any authenticated user (as low as subscriber), or unauthenticated user via a CSRF vector to update them and perform such attack.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2021-24618?

It affects 1 product.


Products: Wbolt Donate With Qrcode.

## How do I fix CVE-2021-24618?

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

## Is CVE-2021-24618 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-24618 and fix it if it is affected.

What it is: CVE-2021-24618 is a medium-severity cross-site scripting vulnerability in Unknown Donate With QRCode, published on 20 Sep 2021. 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-2021-24618 in the wild and no public exploit code.

Affected product: Unknown Donate With QRCode. 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-2021-24618/ (Markdown: https://insights.sbomify.com/CVE-2021-24618/index.md)
```

## Sources

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

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