Is Inquiry form to posts or pages safe to use?

Laskyr does not give safety verdicts. Inquiry form to posts or pages is closed on wordpress.org. Closed on 2026-03-31 (reason given: Security Issue). Closed plugins get no updates through WordPress, so new security holes will not be fixed for you. Keep Inquiry form to posts or pages on the latest version and remove it if you do not use it.

Which versions of Inquiry form to posts or pages are vulnerable?

Known issues on record (newest first): Cross-site request forgery (CSRF) (1.0 and older); Stored cross-site scripting (XSS) (1.0 and older). The full list with sources is on this page.

What should I do if my Inquiry form to posts or pages is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update inquiry-form-to-posts-or-pages). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · inquiry-form-to-posts-or-pages · data as of 2026-11-04

Is Inquiry form to posts or pages safe? Known vulnerabilities and latest version

Status: Closed 2026-03-31
Known issues on record: 2
Unpatched in latest: 0

What to do

Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.

With WP-CLI, once you have a replacement: wp plugin deactivate inquiry-form-to-posts-or-pages && wp plugin delete inquiry-form-to-posts-or-pages

Check your version

Known vulnerabilities

2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 2 record(s) do not state which versions are affected.

medium 4.3 CVE-2026-6293 · published 2026-04-15

Cross-site request forgery (CSRF) in Inquiry form to posts or pages (1.0 and older)

Affected: 1.0 and older
Fixed in: unknown
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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.

NVD CVE-2026-6293 Wordfence advisory Plugin source

medium 4.4 CVE-2026-5169 · published 2026-04-08

Stored cross-site scripting (XSS) in Inquiry form to posts or pages (1.0 and older)

Affected: 1.0 and older
Fixed in: unknown
Access needed (per CVSS): Needs an admin-level account
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The Inquiry Form to Posts or Pages plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'Form Header' field in versions up to and including 1.0. This is due to insufficient input sanitization when saving via update_option() and lack of output escaping when displaying the stored value. The vulnerability exists in two locations: (1) the plugin settings page at inq_form.php line 180 where the value is echoed into an HTML attribute without esc_attr(), and (2) the front-end shortcode output at inquery_form_to_posts_or_pages.php line 139 where the value is output in HTML content without esc_html(). This makes it possible for authenticated attackers with administrator-level access to inject arbitrary web scripts that will execute whenever a user accesses the plugin settings page or views a page containing the [inquiry_form] shortcode.

NVD CVE-2026-5169 Wordfence advisory Plugin source

Recent activity

2026-03-31 — closed on wordpress.org (Security Issue).
2026-04-15 — Cross-site request forgery (CSRF) disclosed (CVE-2026-6293), fix version not stated.
2026-04-08 — Stored cross-site scripting (XSS) disclosed (CVE-2026-5169), fix version not stated.

Free. We check the CVE feeds every day and email you only when a new issue for Inquiry form to posts or pages (inquiry-form-to-posts-or-pages) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Cross-site request forgery (CSRF) (1) · Cross-site scripting (XSS) (1)

Where this data comes from

Version, last update, installs, closure: wordpress.org/plugins/inquiry-form-to-posts-or-pages (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/inquiry-form-to-posts-or-pages"><img src="https://laskyr.com/plugins/inquiry-form-to-posts-or-pages/badge.svg" alt="Inquiry form to posts or pages vulnerability status"></a>

← Check another plugin · Free hacked-site scan