# CVE-2023-2517: Metform Elementor Contact Form Builder <= 3.3.2 - Cross-Site Request Forgery via permalink_setup

> Unauthenticated attackers can trick administrators into changing permalink settings via forged requests in the Metform Elementor Contact Form Builder plugin.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Jul 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-8v66-v52g-2mp3

## What is CVE-2023-2517?

CVE-2023-2517 is a medium-severity vulnerability in roxnor MetForm – Contact Form, Survey, Quiz, & Custom Form Builder for Elementor, published on 12 Jul 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Metform Elementor Contact Form Builder plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.3.2. This is due to missing or incorrect nonce validation on the permalink_setup function. This makes it possible for unauthenticated attackers to change the permalink structure via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. While nonce verification is implemented, verification only takes place when a nonce is provided.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Wpmet Metform Elementor Contact Form Builder.

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

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

## Is CVE-2023-2517 being exploited?

There is no known exploitation of CVE-2023-2517 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-2517 and fix it if it is affected.

What it is: CVE-2023-2517 is a medium-severity vulnerability in roxnor MetForm – Contact Form, Survey, Quiz, & Custom Form Builder for Elementor, published on 12 Jul 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-2517 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-2517/ (Markdown: https://insights.sbomify.com/CVE-2023-2517/index.md)
```

## Sources

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

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