Blog

"Prevention is cheaper than a breach"

Home / Threats / CVE-2026-10077

CVE-2026-10077 - Before 5 Theme

CVE-2026-10077

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.

CVE-2026-10077

MEDIUM CVSS 6.8 Published 2026-07-02 Updated 2026-07-02
AI Risk Elevated (58/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P3 Priority
Severity Band MEDIUM
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
Affected Components 2
Reference Links 1
AI Risk Engine Elevated (58/100)
Exploitability Medium
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2026-07-02 CVE published and first recorded in the threat feed.
  2. 2026-07-02 Record updated with latest vulnerability metadata.
  3. 2026-07-02 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 19 days ago

AI enriched 19 days ago (2026-07-02 19:18 UTC)

Technical Summary

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.

Potential Impact

Severity is MEDIUM (CVSS 6.8). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as Medium based on severity and technical exposure profile.

Primary risk drivers: severity and technical exposure profile

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 58/100 (Elevated, Medium) with priority P3 Priority. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Before 5 THEME · before-5 Affected: < 5.0.35 Fixed in: 5.0.35
Yootheme THEME · yootheme Affected: < 5.0.35 Fixed in: 5.0.35
Scroll to top