# CVE-2025-2802: LayoutBoxx <= 0.3.1 - Unauthenticated Arbitrary Shortcode Execution

> Unauthenticated attackers can execute arbitrary shortcodes in the LayoutBoxx WordPress plugin due to improper validation, potentially leading to code execution.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 May 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-vp63-f79x-pvwj

## What is CVE-2025-2802?

CVE-2025-2802 is a high-severity code injection vulnerability in LayoutBoxx, published on 6 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The LayoutBoxx plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 0.3.1. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2025-2802?


## How do I fix CVE-2025-2802?

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

## Is CVE-2025-2802 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2802 and fix it if it is affected.

What it is: CVE-2025-2802 is a high-severity code injection vulnerability in LayoutBoxx, published on 6 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-2802 in the wild and no public exploit code.

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

## Sources

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

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