WordPress GZSEO plugin <= 2.0.14 - Broken Access Control vulnerability

published 2026-03-25 7mo ago modified 2026-06-17 4mo ago also EUVD-2026-15727

cvss: 6.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 16%
public exploits: 0; none known

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.

Is CVE-2026-25437 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: 7mo ago (2026-03-26)

Exploit prediction

0.25% chance of exploitation in the next 30 days, higher than 16% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

Affected products

سید محمدامین هاشمی GZSEO

Classification

Weakness

CWE-862 Missing Authorization

Technology feeds

WordPress rss critical rss

References

patchstack.com /database/Wordpress/Plugin/gzseo/vulnerability/wordpress-gzseo-plugin-2-0-11-broken-access-control-vulnerabili
vdb-entry

Sources

CVE List CVE-2026-25437
NVD CVE-2026-25437

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.