# CVE-2026-6293: Cross-site request forgery in Inquiry form to posts or pages

> Unauthenticated attackers can trick administrators into executing arbitrary scripts via CSRF, leading to stored XSS and potential account takeover.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Apr 2026
- **Updated:** 16 Apr 2026
- **Also known as:** GHSA-89r9-x6mh-w4fq

## What is CVE-2026-6293?

CVE-2026-6293 is a medium-severity vulnerability in udamadu Inquiry form to posts or pages, published on 15 Apr 2026. 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 Inquiry Form to Posts or Pages plugin for WordPress is vulnerable to Cross-Site Request Forgery leading to Stored Cross-Site Scripting in version 1.0. This is due to missing nonce validation on the plugin settings update handler, combined with insufficient input sanitization on all user-supplied fields and missing output escaping when rendering stored values. The settings handler fires solely on the presence of `$_POST['inq_hidden'] == 'Y'` with no call to `check_admin_referer()` and no WordPress nonce anywhere in the form or handler. This makes it possible for unauthenticated attackers to inject arbitrary web scripts via a forged request that tricks a logged-in Administrator into visiting a malicious page.

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

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


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

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

## Is CVE-2026-6293 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6293 is a medium-severity vulnerability in udamadu Inquiry form to posts or pages, published on 15 Apr 2026. 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-2026-6293 in the wild and no public exploit code.

Affected product: udamadu Inquiry form to posts or pages. 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-6293/ (Markdown: https://insights.sbomify.com/CVE-2026-6293/index.md)
```

## Sources

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

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