# CVE-2024-0508: Cross-site scripting in Orbit Fox: Duplicate Page, Menu Icons, SVG Support, Cookie Notice, Custom Fonts & More

> Authenticated attackers can inject arbitrary web scripts via the Pricing Table Elementor Widget, leading to stored XSS execution on victim pages.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 5 Feb 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-r5m6-pgh6-qg26

## What is CVE-2024-0508?

CVE-2024-0508 is a medium-severity cross-site scripting vulnerability in themeisle Orbit Fox: Duplicate Page, Menu Icons, SVG Support, Cookie Notice, Custom Fonts & More, published on 5 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Orbit Fox by ThemeIsle plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Pricing Table Elementor Widget in all versions up to, and including, 2.10.27 due to insufficient input sanitization and output escaping on the user supplied link URL. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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

## Which versions are affected by CVE-2024-0508?

It affects 1 product.


Products: Themeisle Orbit Fox.

## How do I fix CVE-2024-0508?

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

## Is CVE-2024-0508 being exploited?

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

## Other vulnerabilities in themeisle Orbit Fox: Duplicate Page, Menu Icons, SVG Support, Cookie Notice, Custom Fonts & More

- [CVE-2025-22659](https://insights.sbomify.com/CVE-2025-22659/): WordPress Orbit Fox by ThemeIsle plugin <= 2.10.44 - Cross Site Scripting (XSS) vulnerability (medium 6.5)
- [CVE-2021-24158](https://insights.sbomify.com/CVE-2021-24158/): Orbit Fox by ThemeIsle < 2.10.3 - Authenticated Privilege Escalation (medium 6.5)
- [CVE-2024-13183](https://insights.sbomify.com/CVE-2024-13183/): Orbit Fox by ThemeIsle <= 2.10.43 - Authenticated (Contributor+) Stored Cross-Site Scripting via title_tag Parameter (medium 6.4)
- [CVE-2025-0311](https://insights.sbomify.com/CVE-2025-0311/): Orbit Fox by ThemeIsle <= 2.10.43 - Authenticated (Contributor+) Stored Cross-Site Scripting via Pricing Table Widget (medium 6.4)
- [CVE-2024-7778](https://insights.sbomify.com/CVE-2024-7778/): Orbit Fox by ThemeIsle <= 2.10.36 - Authenticated (Author+) Stored Cross-Site Scripting via SVG File Upload (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-0508 and fix it if it is affected.

What it is: CVE-2024-0508 is a medium-severity cross-site scripting vulnerability in themeisle Orbit Fox: Duplicate Page, Menu Icons, SVG Support, Cookie Notice, Custom Fonts & More, published on 5 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-0508 in the wild and no public exploit code.

Affected product: themeisle Orbit Fox: Duplicate Page, Menu Icons, SVG Support, Cookie Notice, Custom Fonts & More. 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-2024-0508/ (Markdown: https://insights.sbomify.com/CVE-2024-0508/index.md)
```

## Sources

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

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