Is Insert Pages safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (3.11.5). As of 2026-11-04. 5 issues are on record for older versions; version 3.11.5 or newer fixes all of them that state a fix. Keep Insert Pages on the latest version (3.11.5) and remove it if you do not use it.

Which versions of Insert Pages are vulnerable?

Known issues on record (newest first): Stored cross-site scripting (XSS) (3.11.4 and older, fixed in 3.11.5); Stored cross-site scripting (XSS) (older than 3.7.5, fixed in 3.7.5); Missing authorization check (older than 3.7.0, fixed in 3.7.0); Cross-site scripting (XSS) (older than 3.7.0, fixed in 3.7.0); Path traversal / file read (older than 3.2.4, fixed in 3.2.4). The full list with sources is on this page.

What is the latest version of Insert Pages?

3.11.5, according to wordpress.org (last updated 2026-06-19). It has 30,000+ active installs.

What should I do if my Insert Pages is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update insert-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 · insert-pages · data as of 2026-11-04

Is Insert Pages safe? Known vulnerabilities and latest version

Latest version: 3.11.5
Last updated: 2026-06-19
Active installs: 30,000+
Known issues on record: 5
Unpatched in latest: 0
Tested up to WP: 7.0.8

Insert Pages lets you embed any WordPress content (e.g., pages, posts, custom post types) into other WordPress content using the Shortcode API. — by Paul Ryan

What to do

Update to the latest version (3.11.5). Anything older than 3.11.5 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get insert-pages --field=version shows what you run; wp plugin update insert-pages updates it.

Check your version

Known vulnerabilities

5 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.

medium 6.4 CVE-2026-10089 · published 2026-07-02

Stored cross-site scripting (XSS) in Insert Pages (3.11.4 and older)

Affected: 3.11.4 and older
Fixed in: 3.11.5 *
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The Insert Pages plugin for WordPress is vulnerable to Stored Cross-Site Scripting via post custom field keys (meta key names) in all versions up to, and including, 3.11.4. This is due to insufficient output escaping in the the_meta() function: while the custom field VALUE is sanitized with wp_kses_post(), the custom field KEY ($key) is interpolated into the rendered HTML (lines 1786-1791) and echoed (line 1806) without any escaping when an inserted page is rendered with the [insert page='ID' display='all'] shortcode. This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

NVD CVE-2026-10089 Wordfence advisory Code change (fix)Plugin source

medium 5.4 CVE-2022-4483 · published 2023-01-16

Stored cross-site scripting (XSS) in Insert Pages (older than 3.7.5)

Affected: older than 3.7.5
Fixed in: 3.7.5
Access needed (per CVSS): Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

The Insert Pages WordPress plugin before 3.7.5 does not validate and escape some of its shortcode attributes before outputting them back in the page, which could allow users with a role as low as contributor to perform Stored Cross-Site Scripting attacks which could be used against high privilege users such as admins.

NVD CVE-2022-4483 WPScan advisory

medium 4.3 CVE-2021-24851 · published 2021-11-17

Missing authorization check in Insert Pages (older than 3.7.0)

Affected: older than 3.7.0
Fixed in: 3.7.0
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: NVD analysis · score by NVD

Details from the advisory

The Insert Pages WordPress plugin before 3.7.0 allows users with a role as low as Contributor to access content and metadata from arbitrary posts/pages regardless of their author and status (ie private), using a shortcode. Password protected posts/pages are not affected by such issue.

NVD CVE-2021-24851 WPScan advisory Code change (fix)

medium 5.4 CVE-2021-24850 · published 2021-11-17

Cross-site scripting (XSS) in Insert Pages (older than 3.7.0)

Affected: older than 3.7.0
Fixed in: 3.7.0
Access needed (per CVSS): Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from: NVD analysis · score by NVD

Details from the advisory

The Insert Pages WordPress plugin before 3.7.0 adds a shortcode that prints out other pages' content and custom fields. It can be used by users with a role as low as Contributor to perform Cross-Site Scripting attacks by storing the payload/s in another post's custom fields.

NVD CVE-2021-24850 WPScan advisory

critical 9.1 CVE-2017-18586 · published 2019-08-22

Path traversal / file read in Insert Pages (older than 3.2.4)

Affected: older than 3.2.4
Fixed in: 3.2.4
Access needed (per CVSS): No login needed
Range from: NVD analysis · score by NVD

Details from the advisory

The insert-pages plugin before 3.2.4 for WordPress has directory traversal via custom template paths.

NVD CVE-2017-18586 wordpress.org

Recent activity

2026-06-19 — latest release on wordpress.org (3.11.5).
2026-07-02 — Stored cross-site scripting (XSS) disclosed (CVE-2026-10089), fixed in 3.11.5.
2023-01-16 — Stored cross-site scripting (XSS) disclosed (CVE-2022-4483), fixed in 3.7.5.
2021-11-17 — Missing authorization check disclosed (CVE-2021-24851), fixed in 3.7.0.

Free. We check the CVE feeds every day and email you only when a new issue for Insert Pages (insert-pages) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Cross-site scripting (XSS) (3) · Missing authorization (1) · Path traversal and file read (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/insert-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/insert-pages"><img src="https://laskyr.com/plugins/insert-pages/badge.svg" alt="Insert Pages vulnerability status"></a>

← Check another plugin · Free hacked-site scan

Is Insert Pages safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (3.11.5)

What to do

Check your version

Known vulnerabilities

Stored cross-site scripting (XSS) in Insert Pages (3.11.4 and older)

Stored cross-site scripting (XSS) in Insert Pages (older than 3.7.5)

Missing authorization check in Insert Pages (older than 3.7.0)

Cross-site scripting (XSS) in Insert Pages (older than 3.7.0)

Path traversal / file read in Insert Pages (older than 3.2.4)

Recent activity

Get an email when Insert Pages has a new vulnerability

Browse vulnerabilities

Where this data comes from