WordPress WordPress Dating Theme theme <= 11.2.0 - Broken Access Control vulnerability

published 2026-06-17 4mo ago modified 2026-10-25 15d ago also EUVD-2026-37662

cvss: 8.6; 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 17%
public exploits: 0; none known

Unauthenticated Broken Access Control in WordPress Dating Theme <= 11.2.0 versions.

Is CVE-2026-22343 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: 4mo ago (2026-06-17)

Exploit prediction

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

CVSS scores

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

Affected products

PremiumPress Limited. WordPress Dating Theme

Classification

Weakness

CWE-862 Missing Authorization

Technology feeds

WordPress rss critical rss

References

patchstack.com /database/wordpress/theme/da10/vulnerability/wordpress-wordpress-dating-theme-theme-11-2-0-broken-access-contr
vdb-entry

Sources

CVE List CVE-2026-22343
NVD CVE-2026-22343

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.