dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-10089

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Insert Pages WordPress plugin (versions up to 3.11.4) contains a stored XSS vulnerability in its the_meta() function. While custom field VALUES are properly sanitized with wp_kses_post(), the custom field KEYS are directly interpolated into HTML output without any escaping (lines 1786-1791, echoed line 1806). Authenticated attackers with author-level access can inject malicious scripts via custom field meta key names that execute whenever users access pages containing the [insert page='ID' display='all'] shortcode.

MitigationUpdate the Insert Pages plugin to version 3.11.5 or later which applies esc_attr() or equivalent escaping to meta key names before output. As an interim measure, restrict custom field creation/editing to trusted administrators only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Insert Pages plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Insert Pages' in the list. Note whether it is active or inactive.
    Affected if The plugin is installed and active - the vulnerability only applies when the plugin is active.
  2. Check Insert Pages plugin version
    Click 'View details' on the Insert Pages plugin in the plugins list, or check the main plugin file (insert-pages/insert-pages.php) for the 'Version' header comment. Compare against the affected range: versions 3.11.4 and earlier are vulnerable.
    Affected if The installed version is 3.11.4 or earlier.
  3. Identify custom field keys in the database
    Query the wp_postmeta table (or use a plugin like WP Data Access) to examine meta_key values in the database. Look for custom field keys that may contain HTML/script tags or unusual characters that could indicate malicious input.
    Affected if Any custom field keys contain unescaped HTML or script tags that would execute when rendered by the_meta().
  4. Locate pages using the vulnerable shortcode
    Search the wp_posts table for content containing the shortcode pattern [insert_page display='all']. The vulnerability triggers when this specific shortcode variant is used.
    Affected if Any published content contains the [insert_page='ID' display='all'] shortcode, which invokes the vulnerable the_meta() function.
  5. Confirm the_meta function is called by the shortcode
    Examine the Insert Pages plugin file around lines 1786-1806 (the the_meta() function) to verify that when display='all' is used, the meta keys are output without escaping. Check if your content triggers this code path.
    Affected if The plugin code shows meta keys are directly output without esc_attr() or similar escaping, and your content uses the vulnerable shortcode.

A user is affected if the Insert Pages plugin version is 3.11.4 or earlier, the plugin is active, and content exists using the [insert_page display='all'] shortcode that renders custom field meta keys.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Insert Pages plugin to version 3.11.5 or later which applies esc_attr() or equivalent escaping to meta key names before output. As an interim measure, restrict custom field creation/editing to trusted administrators only.

Recommended fix Moderate confidence

3.11.5

  1. Update the Insert Pages WordPress plugin to version 3.11.5 or later
  2. Verify the update was successful by checking the Plugins page in WordPress admin
  3. Test that the [insert page] shortcode still functions correctly after the update
  4. Confirm that custom field keys are now properly escaped when rendered

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10089 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10089 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data