# CVE-2024-6447: FULL <= 3.1.12 - Unauthenticated Stored Cross-Site Scripting via License Plan Parameter

> Unauthenticated attackers can inject scripts via the license plan parameter, executing them in admin sessions to potentially take over accounts.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-7w5c-g3qv-vx8v

## What is CVE-2024-6447?

CVE-2024-6447 is a high-severity cross-site scripting vulnerability in fullservices FULL – Cliente, published on 10 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The FULL – Cliente plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the license plan parameter in all versions up to, and including, 3.1.12 due to insufficient input sanitization and output escaping as well as missing authorization and capability checks on the related functions. This makes it possible for unauthenticated attackers to inject arbitrary web scripts that will execute whenever an administrative user accesses wp-admin dashboard

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

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


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

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

## Is CVE-2024-6447 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-6447 is a high-severity cross-site scripting vulnerability in fullservices FULL – Cliente, published on 10 Jul 2024. 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-2024-6447 in the wild and no public exploit code.

Affected product: fullservices FULL – Cliente. 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-6447/ (Markdown: https://insights.sbomify.com/CVE-2024-6447/index.md)
```

## Sources

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

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