Plugins · gzseo · data as of 2026-11-04
Is GZSEO safe? Known vulnerabilities and latest version
- Latest version
- 2.0.15
- Last updated
- 2026-09-29
- Active installs
- 400+
- Known issues on record
- 2
- Unpatched in latest
- 0
- Tested up to WP
- 7.0.8 · PHP 7.4+
GZSEO is an SEO assistant plugin designed to make content updates easier for SEO professionals. — by سید محمدامین هاشمی
What to do
- Update to the latest version (2.0.15). Anything older than 2.0.15 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get gzseo --field=version shows what you run; wp plugin update gzseo updates it.
Check your version
Known vulnerabilities
2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
medium 6.5 CVE-2026-25437 · published 2026-03-25
Missing authorization check in GZSEO (2.0.14 and older)
- Affected
- 2.0.14 and older
- Fixed in
- 2.0.15 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Missing Authorization vulnerability in سید محمدامین هاشمی GZSEO gzseo allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects GZSEO: from n/a through <= 2.0.14.
medium 6.4 CVE-2025-14941 · published 2026-01-24
Stored cross-site scripting (XSS) in GZSEO (2.0.11 and older)
- Affected
- 2.0.11 and older
- Fixed in
- 2.0.12 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The GZSEO plugin for WordPress is vulnerable to authorization bypass leading to Stored Cross-Site Scripting in all versions up to, and including, 2.0.11. This is due to missing capability checks on multiple AJAX handlers combined with insufficient input sanitization and output escaping on the embed_code parameter. This makes it possible for authenticated attackers, with contributor level access and above, to inject arbitrary content into any post on the site that will execute whenever a user accesses an injected page.
NVD CVE-2025-14941Wordfence advisoryCode change (fix)Plugin source
Recent activity
- 2026-09-29 — latest release on wordpress.org (2.0.15).
- 2026-03-25 — Missing authorization check disclosed (CVE-2026-25437), fixed in 2.0.15.
- 2026-01-24 — Stored cross-site scripting (XSS) disclosed (CVE-2025-14941), fixed in 2.0.12.
Get an email when GZSEO has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for GZSEO (gzseo) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Missing authorization (1) · Cross-site scripting (XSS) (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/gzseo (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/gzseo"><img src="https://laskyr.com/plugins/gzseo/badge.svg" alt="GZSEO vulnerability status"></a>