# CVE-2023-2582: Cross-site scripting in Strikingly

> Prototype pollution in Strikingly CMS allows reflected XSS via crafted links, enabling arbitrary JavaScript execution in the victim's browser.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 May 2023
- **Updated:** 28 Jan 2025
- **Also known as:** GHSA-w545-g5fp-84fq

## What is CVE-2023-2582?

CVE-2023-2582 is a medium-severity cross-site scripting vulnerability in Strikingly, published on 8 May 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A prototype pollution vulnerability exists in Strikingly CMS which can result in reflected cross-site scripting (XSS) in affected applications and sites built with Strikingly. The vulnerability exists because of Strikingly JavaScript library parsing the URL fragment allows access to the __proto__ or constructor properties and the Object prototype. By leveraging an embedded gadget like jQuery, an attacker who convinces a victim to visit a specially crafted link could achieve arbitrary javascript execution in the context of the user's browser.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

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

It affects 1 product.


Products: Strikingly Strikingly.

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

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

## Is CVE-2023-2582 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-2582 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2023-2582 is a medium-severity cross-site scripting vulnerability in Strikingly, published on 8 May 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-2582 exists.

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

## Sources

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

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