CVE-2026-78295

Xagio SEO & AEO – AI SEO for Google Rankings & AI Visibility <= 7.1.0.43 - Cross-Site Request Forgery

2026-09-16 18:12
Matheo Beuve

Strategic Overview

Status
Patched in 7.1.0.44
Affected Plugin
Xagio SEO & AEO – AI SEO for Google Rankings & AI Visibility
Affected Version
<= 7.1.0.43
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2026-78295
View all Xagio SEO & AEO – AI SEO for Google Rankings & AI Visibility vulnerabilities

At a glance

CVE-2026-78295 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Xagio SEO & AEO WordPress plugin, affecting versions <= 7.1.0.43. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 7.1.0.44; sites on affected versions should update now. Disclosed September 2026, reported by Matheo Beuve.

Vulnerability Overview

The Xagio SEO & AEO – AI SEO for Google Rankings & AI Visibility plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 7.1.0.43. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to perform an unauthorized action via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Xagio SEO & AEO <= 7.1.0.43 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Xagio SEO & AEO the fix is 7.1.0.44: builds <= 7.1.0.43 are affected, anything from 7.1.0.44 onward is not.

Remediation

Update to version 7.1.0.44, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Xagio SEO & AEO: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Xagio SEO & AEO 7.1.0.44 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-78295https://www.wordfence.com/threat-intel/vulnerabilities/id/7f250c22-5615-4223-a7d0-8467cb2f8541https://nvd.nist.gov/vuln/detail/CVE-2026-78295

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C