# CVE-2025-6212: Ultra Addons for Contact Form 7 3.5.11 - 3.5.19 - Unauthenticated Stored Cross-Site Scripting via Database module

> Unauthenticated attackers can inject arbitrary scripts via field names in the Database module, executing them in admin browsers.

- **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:** 26 Jun 2025
- **Updated:** 26 Jun 2025
- **Also known as:** GHSA-cqrx-xvwc-3fwp

## What is CVE-2025-6212?

CVE-2025-6212 is a high-severity cross-site scripting vulnerability in themefic Ultra Addons for Contact Form 7, published on 26 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Ultra Addons for Contact Form 7 plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Database module in versions 3.5.11 to 3.5.19 due to insufficient input sanitization and output escaping. The unfiltered field names are stored alongside the sanitized values. Later, the admin-side AJAX endpoint ajax_get_table_data() returns those raw names as JSON column headers, and the client-side DataTables renderer injects them directly into the DOM without any HTML encoding. This makes it possible for unauthenticated attackers 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-2025-6212?

It affects 1 product.


Products: Themefic Ultimate Addons for Contact Form 7.

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

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

## Is CVE-2025-6212 being exploited?

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

## Other vulnerabilities in themefic Ultra Addons for Contact Form 7

- [CVE-2023-1615](https://insights.sbomify.com/CVE-2023-1615/): SQL injection in Ultimate Addons for Contact Form 7 (high 8.8)
- [CVE-2023-30495](https://insights.sbomify.com/CVE-2023-30495/): WordPress Ultimate Addons for Contact Form 7 Plugin <= 3.1.23 is vulnerable to SQL Injection (high 8.5)
- [CVE-2022-47586](https://insights.sbomify.com/CVE-2022-47586/): WordPress Ultimate Addons for Contact Form 7 Plugin <= 3.1.23 is vulnerable to SQL Injection (high 8.2)
- [CVE-2025-6220](https://insights.sbomify.com/CVE-2025-6220/): Ultimate Addons for Contact Form 7 <= 3.5.12 - Authenticated (Administrator+) Arbitrary File Upload via 'save_options' (high 7.2)
- [CVE-2023-49766](https://insights.sbomify.com/CVE-2023-49766/): WordPress Ultimate Addons for Contact Form 7 Plugin <= 3.2.0 is vulnerable to Cross Site Scripting (XSS) (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-6212 is a high-severity cross-site scripting vulnerability in themefic Ultra Addons for Contact Form 7, published on 26 Jun 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-6212 in the wild and no public exploit code.

Affected product: themefic Ultra Addons for Contact Form 7. 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-6212/ (Markdown: https://insights.sbomify.com/CVE-2025-6212/index.md)
```

## Sources

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

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