Xagio SEO & AEO · Security record
Is Xagio SEO & AEO safe?
One known vulnerability affects the current version (7.1.0.47), and it has no fix yet.
Checked 4 days ago against the WPVulnerability database, for version 7.1.0.47.
How it’s looked after
- Last release
- Nov 6, 2026 (3 days ago)
- Releases in the last year
- 22
- Tested up to
- WordPress 7.0.8
- Active installs
- 10K+
7 known vulnerabilities
- 1 critical
- 3 high
- 3 medium
1 affects the current version. 1 has no fix yet.
Disclosed each year
- 20254
- 20263
Every known vulnerability in Xagio SEO & AEO
Newest first, with any that affect the current version at the top.
- medium
Missing Authorization
Affects the current version · No fix yet · CVE-2025-63025 · Dec 4, 2025 · Wordfence
Fixed in 7.1.0.44 · CVE-2026-78295 · Mar 12, 2026 · Wordfence
Fixed in 7.1.0.31 · CVE-2026-24968 · Mar 12, 2026 · Wordfence
Fixed in 7.1.0.31 · CVE-2025-14438 · Jan 5, 2026 · Wordfence
Fixed in 7.1.0.6 · CVE-2024-13807 · Aug 27, 2025 · Wordfence
Fixed in 7.1.0.17 · CVE-2025-3302 · Jun 10, 2025 · Wordfence
Fixed in 7.0.0.21 · CVE-2025-24702 · Jan 24, 2025 · Wordfence
Questions about Xagio SEO & AEO’s security
Is Xagio SEO & AEO safe to use?
Yes: 1 known vulnerability affects version 7.1.0.47, according to WPVulnerability’s database. Until a fixed version is out, weigh the risk, or switch to an alternative.
Does Xagio SEO & AEO have known security vulnerabilities?
Yes: 1 known vulnerability affects version 7.1.0.47, according to WPVulnerability’s database.
Is Xagio SEO & AEO still maintained?
Yes. Its last release was 3 days ago. No support threads were opened in the last two months.
Is Xagio SEO & AEO compatible with the latest WordPress?
It’s tested up to WordPress 7.0.8, one version behind the current 7.1. Authors often update this line a few weeks after a release.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.