# CVE-2023-0708: Cross-site scripting in MetForm – Contact Form, Survey, Quiz, & Custom Form Builder for Elementor

> Authenticated attackers can inject arbitrary scripts via the mf_first_name shortcode, leading to stored XSS execution when victims visit crafted links.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Jun 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-3gr8-qjqc-www6

## What is CVE-2023-0708?

CVE-2023-0708 is a medium-severity cross-site scripting vulnerability in roxnor MetForm – Contact Form, Survey, Quiz, & Custom Form Builder for Elementor, published on 9 Jun 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The Metform Elementor Contact Form Builder for WordPress is vulnerable to Cross-Site Scripting by using the 'mf_first_name' shortcode to echo unescaped form submissions in versions up to, and including, 3.3.0. This allows authenticated attackers, with contributor-level permissions or above, to inject arbitrary web scripts in pages that will execute when the victim visits a a page containing the shortcode when the submission id is present in the query string. Note that getting the JavaScript to execute requires user interaction as the victim must visit a crafted link with the form entry id, but the script itself is stored in the site database.

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

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

It affects 1 product.


Products: Wpmet Metform Elementor Contact Form Builder.

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

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

## Is CVE-2023-0708 being exploited?

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

## Other vulnerabilities in roxnor MetForm – Contact Form, Survey, Quiz, & Custom Form Builder for Elementor

- [CVE-2023-0721](https://insights.sbomify.com/CVE-2023-0721/): Metform Elementor Contact Form Builder <= 3.3.0 - Unauthenticated CSV Injection (high 8.3)
- [CVE-2023-0714](https://insights.sbomify.com/CVE-2023-0714/): Metform Elementor Contact Form Builder <= 3.2.4 - Unauthenticated Double-Extension Arbitrary File Upload (high 8.1)
- [CVE-2022-1442](https://insights.sbomify.com/CVE-2022-1442/): Metform Elementor Contact Form Builder <= 2.1.3 - Sensitive Information Disclosure (high 7.5)
- [CVE-2023-0084](https://insights.sbomify.com/CVE-2023-0084/): Metform Elementor Contact Form Builder <= 3.1.2 - Unauthenticated Stored Cross-Site Scripting (high 7.2)
- [CVE-2023-0688](https://insights.sbomify.com/CVE-2023-0688/): Information disclosure in MetForm – Contact Form, Survey, Quiz, & Custom Form Builder for Elementor (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-0708 is a medium-severity cross-site scripting vulnerability in roxnor MetForm – Contact Form, Survey, Quiz, & Custom Form Builder for Elementor, published on 9 Jun 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-0708 in the wild and no public exploit code.

Affected product: roxnor MetForm – Contact Form, Survey, Quiz, & Custom Form Builder for Elementor. 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-0708/ (Markdown: https://insights.sbomify.com/CVE-2023-0708/index.md)
```

## Sources

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

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