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

CVE-2026-27402

HIGH · 7.1 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 →
78/100
Remediation priority · High
Remotely reachable No privileges 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
Unauthenticated Cross Site Scripting (XSS) in Kids Life | Children School WordPress <= 5.2 versions.

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

Unauthenticated Cross Site Scripting (XSS) vulnerability in the Kids Life WordPress theme affecting versions 5.2 and below. An attacker can inject malicious scripts into the vulnerable site without requiring authentication, potentially leading to session hijacking or credential theft.

MitigationUpdate Kids Life theme to version greater than 5.2. If no update is available, remove or replace the theme until a patch is released.

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 Kids Life theme is installed
    Check the wp-content/themes/ directory for a 'kids-life' or 'kids_life' folder, or view installed themes via WordPress admin at Appearance > Themes
    Affected if The Kids Life theme folder exists in the WordPress themes directory
  2. Determine the installed theme version
    Open wp-content/themes/kids-life/style.css and locate the 'Version:' declaration in the file header comments, or view theme details in WordPress admin at Appearance > Themes > Theme Details
    Affected if The reported version is 5.2 or any version below 5.2 (such as 5.1, 5.0, etc.)
  3. Identify vulnerable input fields
    Review the theme files for form handlers and search functionality, typically in functions.php, search.php, or header.php, looking for $_GET, $_POST, or $_REQUEST parameters that are output without sanitization
    Affected if User-supplied parameters are directly echoed to HTML without escaping functions like esc_html() or esc_attr()
  4. Check for existing script injection
    Search the WordPress database and published content for suspicious script tags, particularly in comment fields, post content, or theme customizer inputs, using tools like phpMyAdmin or WP-CLI: wp db query "SELECT * FROM wp_posts WHERE post_content LIKE '%<script%'"
    Affected if Malicious JavaScript tags are found stored in the database or rendered on pages

Your environment is affected if Kids Life theme version 5.2 or lower is installed and user input is reflected in pages without proper sanitization

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 Kids Life theme to version greater than 5.2. If no update is available, remove or replace the theme until a patch is released.

Recommended fix Moderate confidence

Latest available version of Kids Life theme from the official developer (version higher than 5.2)

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to Dashboard > Appearance > Themes
  3. 3. Check the current version of the Kids Life theme to confirm it is version 5.2 or below
  4. 4. If a newer version of the Kids Life theme is available from the theme developer, click 'Update' to install the fixed version
  5. 5. If no update is available from the theme developer, consider these alternatives: temporarily switch to a secure default WordPress theme, or remove the theme entirely if not in use, or contact the theme developer directly to request a security patch
  6. 6. After updating, verify the XSS vulnerability is resolved by testing input fields that could be exploited
  7. 7. Consider implementing a Web Application Firewall (WAF) as an additional layer of protection
Caveat Review theme customizations after upgrade as they may need to be reapplied if the new version includes template changes

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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