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

CVE-2026-6174

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-14
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

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 CC Child Pages plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'more' parameter in all versions up to, and including, 2.1.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-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 CC Child Pages WordPress plugin up to version 2.1.1 has a stored XSS vulnerability in the 'more' parameter due to insufficient input sanitization and output escaping. Authenticated attackers with Contributor-level permissions or higher can inject malicious JavaScript that executes whenever users view affected pages.

MitigationUpdate the CC Child Pages plugin to version 2.1.2 or later which contains proper input sanitization and output escaping for the 'more' parameter.

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. Confirm CC Child Pages plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'CC Child Pages' in the list. Alternatively, check the /wp-content/plugins/cc-child-pages/ directory exists on the server.
    Affected if The plugin is installed and active in WordPress
  2. Check the installed plugin version
    In WordPress admin > Plugins > Installed Plugins, find CC Child Pages and view the version number displayed below the plugin name. Or read the version from the plugin's main PHP file header.
    Affected if The version is 2.1.1 or earlier (any version up to and including 2.1.1)
  3. Identify pages using the 'more' parameter
    Search WordPress page content or shortcode attributes for patterns like 'more="' or '[cc_child_pages ... more=' to find where the vulnerable parameter is being used.
    Affected if Any page or shortcode is using the 'more' parameter with user-supplied content
  4. Inspect stored content for injected scripts
    Review page content in the WordPress editor where CC Child Pages shortcodes with the 'more' parameter exist. Check for unexpected script tags, event handlers, or suspicious JavaScript in the parameter value.
    Affected if The 'more' parameter contains unsanitized HTML or JavaScript (e.g., <script>, javascript:, onload, onerror, onClick)

You are affected if the CC Child Pages plugin version is 2.1.1 or earlier AND any page uses the 'more' parameter with potentially malicious content that could execute in admin or visitor browsers.

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 CC Child Pages plugin to version 2.1.2 or later which contains proper input sanitization and output escaping for the 'more' parameter.

Recommended fix Moderate confidence

Latest available version on WordPress plugin repository (check for version greater than 2.1.1)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the CC Child Pages plugin
  4. Check if an update is available and update to the latest version
  5. If no update is available, consider temporarily disabling the plugin until a patched version is released
  6. Verify the update was applied successfully

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6174 — 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-6174 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