dbcve.org
VulnerabilityAwaiting classification

CVE-2026-10077

MEDIUM · 6.8 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 →
72/100
Remediation priority · Elevated
Remotely reachable 8 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 yootheme WordPress theme before 5.0.35 does not prevent its bundled front-end framework from treating certain HTML attributes, which are permitted by wp_kses_post(), as markup, allowing users with the Author role to perform Stored Cross-Site Scripting attacks that execute in the browser of any user who views the affected post.

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 yootheme WordPress theme before version 5.0.35 fails to sanitize certain HTML attributes that wp_kses_post() permits, allowing its bundled front-end framework to interpret these attributes as active markup. An attacker with Author-level WordPress privileges can inject malicious attribute-based payloads into posts that persist and execute in the browsers of all users who view those posts.

MitigationUpdate the yootheme theme to version 5.0.35 or later to patch the XSS vulnerability. Alternatively, restrict the Author role's ability to create/edit posts or implement additional output sanitization on the front-end.

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
High
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify installed yootheme theme version
    Access the WordPress dashboard, go to Appearance > Themes, and locate the yootheme theme. The version is typically displayed in the theme details panel. Alternatively, check the style.css file in the theme directory for the 'Version' header comment.
    Affected if The installed version is lower than 5.0.35 (e.g., 5.0.34, 5.0.30, etc.)
  2. Verify Author role permissions
    In WordPress admin, navigate to Users > Roles or check the User Role Editor plugin if installed. Confirm whether the Author role retains the capability to create and edit posts (capability: 'edit_posts').
    Affected if The Author role has the 'edit_posts' capability enabled, allowing authors to create or modify content.
  3. Inspect recent posts for suspicious attributes
    Review recent posts authored by users with Author-level access. Examine the post content in HTML or Text view, looking for unusual attribute patterns such as 'onload=', 'onerror=', 'onclick=', 'javascript:', or data URIs within HTML tags.
    Affected if Posts contain unexpected HTML attribute payloads that were not intentionally added by an administrator.
  4. Check theme framework configuration
    If yootheme theme has a framework configuration file (typically in the theme's config directory), examine it for settings related to HTML attribute processing or content filtering.
    Affected if The framework is configured to process post content through the vulnerable wp_kses_post() path without additional sanitization.

Your environment is affected if the yootheme theme version is below 5.0.35 AND the Author role can create or edit posts, allowing potential XSS injection through HTML attributes.

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 yootheme theme to version 5.0.35 or later to patch the XSS vulnerability. Alternatively, restrict the Author role's ability to create/edit posts or implement additional output sanitization on the front-end.

Recommended fix High confidence

YOOtheme WordPress theme version 5.0.35 or later

  1. 1. Log in to the WordPress admin dashboard with administrator privileges
  2. 2. Navigate to Appearance > Themes
  3. 3. Locate the YOOtheme theme in the list of installed themes
  4. 4. Check the current version of the theme to confirm it is below 5.0.35
  5. 5. If an update is available, click on the theme and select Update, or go to Dashboard > Updates and apply available updates
  6. 6. Verify the theme has been updated to version 5.0.35 or later
  7. 7. Test affected functionality to confirm the XSS vulnerability has been resolved

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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