We’re actively acquiring WordPress agencies. Sell your WordPress business to Freshy.
Let’s discuss

Inquiry Form to Posts or Pages Plugin Vulnerability (CVE-2026-6293)

Nick Paliughi
On this page

Security Alert Summary

The Inquiry Form to Posts or Pages WordPress plugin contains a Cross-Site Request Forgery (CSRF) vulnerability that can lead to Stored Cross-Site Scripting (XSS) in version 1.0. The plugin’s settings update handler lacks nonce validation and relies only on a POST flag, and user-supplied fields are not properly sanitized or escaped when rendered. An attacker can craft a forged request that, if a logged-in Administrator visits a malicious page, results in injected scripts being stored and executed in the administrator’s browser.

CVE Details

  • CVE ID: CVE-2026-6293
  • Affected component: Inquiry Form to Posts or Pages plugin for WordPress
  • Affected versions: version 1.0
  • Published: April 15, 2026 at 7:16:12 AM
  • Last modified: April 15, 2026 at 7:16:12 AM
  • CVSS v3.1: Base score 4.3 (MEDIUM); Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
  • Authentication / Privileges / User interaction: Authentication: none required; Privileges required: none (PR:N); User interaction: required (UI:R)
  • Primary impact: Confidentiality: NONE; Integrity: LOW; Availability: NONE
  • Weakness (CWE): CWE-352 (Cross-Site Request Forgery)

Technical Details

The vulnerability is a CSRF that leads to stored XSS due to missing nonce validation and inadequate input/output handling. The plugin’s settings handler activates solely when $_POST['inq_hidden'] == 'Y' is present, and there is no call to check_admin_referer() or any WordPress nonce in the form or handler. Because the handler relies only on that POST flag, an attacker can cause the handler to process attacker-controlled input via a forged request.

In addition to the missing nonce check, all user-supplied fields lack sufficient input sanitization, and stored values are rendered without proper output escaping. Combined, these flaws allow an attacker to inject arbitrary script into fields that are saved and later rendered in the admin interface. When a logged-in Administrator is tricked into visiting a crafted page, the stored script can execute in the Administrator’s browser context.

The impact observed in the CVE data is limited to integrity (LOW) and does not list confidentiality or availability impacts. The immediate technical consequence is script execution in an administrative context through stored data rendered without escaping, not an automatic full site takeover.

How This Could Impact Your Website

Consider a typical small site workflow: a site owner manages plugins and settings, internal staff members create content, and an external contractor occasionally updates forms or themes. If this plugin is active and an attacker crafts a malicious page that causes the plugin’s settings handler to save attacker-controlled input, a visiting Administrator could trigger the stored script. Practical consequences include modifications to settings or content rendered in the admin interface, or scripts that perform actions available to the Administrator’s browser session.

Because stored XSS can expose email addresses or present targeted content, this increases the risk of targeted phishing or social engineering against staff and contractors who interact with the site. If youre unsure whether your site is affected or how to assess your current user roles and plugins, it may be worth having a professional review.

Recommended Actions

  • Update the affected plugin as soon as a patched version is available.
  • Review and reduce unnecessary user roles, especially contributors and other low-privilege accounts with access to admin areas.
  • Enforce strong passwords and two-factor authentication for editors and administrators.
  • Remove unused or unmaintained plugins to reduce attack surface.
  • Monitor site activity and logs for unusual behavior, particularly settings changes and unexpected stored content.

If youd like help reviewing your plugins, user roles, or overall WordPress security posture, our team at Freshy is happy to help.

References

Nick Paliughihttps://freshysites.com/team/nick-paliughi/
Nick was born in California and now resides in Lake Worth, FL. He has 10 years of experience building and maintaining sites in WordPress, which he is excited to put to use at Freshy. Prior to starting at Freshy in 2022 his focus was on WordPress security & malware removal. When he’s not tending to your website, Nick is installing exhibitions at art galleries and museums in Palm Beach County, and if he’s lucky surfing at the Lake Worth pier.

See our featured website design work

Check out some of the beautiful websites we’ve built for over 2,000 clients.

View projects

We offer WordPress support & maintenance

Shake the stress of ongoing maintenance with plans supported by our team of WordPress experts.

Learn more
Previous Post
Visa Acceptance Solutions Plugin Vulnerability (CVE-2026-3461)
Next Post
e-shot form builder Plugin Vulnerability (CVE-2026-3642)