# CVE-2023-0076: Download Attachments < 1.3 - Contributor+ Stored XSS

> Contributors can inject malicious scripts via shortcode attributes in the Download Attachments plugin, leading to stored XSS attacks.

- **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:** 6 Mar 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-m967-grxx-4qjp

## What is CVE-2023-0076?

CVE-2023-0076 is a medium-severity cross-site scripting vulnerability in Unknown Download Attachments, published on 6 Mar 2023. 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 Download Attachments WordPress plugin before 1.3 does not validate and escape some of its shortcode attributes before outputting them back in a page/post where the shortcode is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks.

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

It affects 1 product.


Products: Dfactory Download Attachments.

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

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

## Is CVE-2023-0076 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-0076 is a medium-severity cross-site scripting vulnerability in Unknown Download Attachments, published on 6 Mar 2023. 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-2023-0076 in the wild and no public exploit code.

Affected product: Unknown Download Attachments. 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-0076/ (Markdown: https://insights.sbomify.com/CVE-2023-0076/index.md)
```

## Sources

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

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