# CVE-2026-3642: e-shot <= 1.0.2 - Missing Authorization to Authenticated (Subscriber+) Form Settings Modification via AJAX

> Authenticated subscribers can modify form field configurations in the e-shot WordPress plugin due to missing authorization checks in an AJAX handler.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** 15 Apr 2026
- **Updated:** 16 Apr 2026
- **Also known as:** GHSA-hrvp-vrhh-gjx9

## What is CVE-2026-3642?

CVE-2026-3642 is a medium-severity missing authorization vulnerability in forfront e-shot, published on 15 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The e-shot™ form builder plugin for WordPress is vulnerable to Missing Authorization in all versions up to and including 1.0.2. The eshot_form_builder_update_field_data() AJAX handler lacks any capability checks (current_user_can()) or nonce verification (check_ajax_referer()/wp_verify_nonce()). The function is registered via the wp_ajax_ hook, making it accessible to any authenticated user. This makes it possible for authenticated attackers, with Subscriber-level access and above, to modify form field configurations including mandatory status, field visibility, and form display preferences via the eshot_form_builder_update_field_data AJAX action.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-3642?


## How do I fix CVE-2026-3642?

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

## Is CVE-2026-3642 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-3642 and fix it if it is affected.

What it is: CVE-2026-3642 is a medium-severity missing authorization vulnerability in forfront e-shot, published on 15 Apr 2026. 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-2026-3642 in the wild and no public exploit code.

Affected product: forfront e-shot. 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-2026-3642/ (Markdown: https://insights.sbomify.com/CVE-2026-3642/index.md)
```

## Sources

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

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