WordPress WP Sort Order plugin <= 1.3.5 - Broken Access Control vulnerability

published 2026-08-18 2mo ago modified 2026-10-22 18d ago also EUVD-2026-60892

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

Unauthenticated Broken Access Control in WP Sort Order <= 1.3.5 versions.

Is CVE-2026-28567 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: 2mo ago (2026-08-18)

Exploit prediction

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

CVSS scores

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

Affected products

Fahad Mahmood WP Sort Order

Classification

Weakness

CWE-862 Missing Authorization

Technology feeds

WordPress rss critical rss

References

patchstack.com /database/wordpress/plugin/wp-sort-order/vulnerability/wordpress-wp-sort-order-plugin-1-3-5-broken-access-cont
vdb-entry

Sources

CVE List CVE-2026-28567
NVD CVE-2026-28567

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.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.