The Kirki – Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 6.1.1. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with custom-level access and above, to read arbitrary user metadata and sensitive user record fields — including email address, assigned roles, registration date, and any user_meta values — belonging to any WordPress user including administrators, by supplying a target user ID with a user-type context to the frontend collection endpoint.
CVE-2026-18347
Score 4.3 from GitHub Security Advisory published 2026-08-16. a secondary CVSS source baseline 4.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(high)
- EG Risk
- 19(Track)EG Risk 19/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity43% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 23%
- KEV
- Not listed
Published
August 16, 2026
Last Modified
August 20, 2026
References (12)
- security@wordfencehttps://plugins.trac.wordpress.org/browser/kirki/tags/6.0.9/includes/API/Frontend/Controllers/CollectionController.php#L97
- security@wordfencehttps://plugins.trac.wordpress.org/browser/kirki/tags/6.0.9/includes/API/Frontend/Controllers/FrontendRESTController.php#L42
- security@wordfencehttps://plugins.trac.wordpress.org/browser/kirki/tags/6.0.9/includes/API/Frontend/Controllers/FrontendRESTController.php#L82
- security@wordfencehttps://plugins.trac.wordpress.org/browser/kirki/tags/6.0.9/includes/Ajax/Users.php#L227
- security@wordfencehttps://plugins.trac.wordpress.org/browser/kirki/tags/6.0.9/includes/HelperFunctions.php#L1098
- security@wordfencehttps://plugins.trac.wordpress.org/browser/kirki/tags/6.1.1/includes/API/Frontend/Controllers/CollectionController.php#L97
- security@wordfencehttps://plugins.trac.wordpress.org/browser/kirki/tags/6.1.1/includes/API/Frontend/Controllers/FrontendRESTController.php#L42
- security@wordfencehttps://plugins.trac.wordpress.org/browser/kirki/tags/6.1.1/includes/API/Frontend/Controllers/FrontendRESTController.php#L82
- security@wordfencehttps://plugins.trac.wordpress.org/browser/kirki/tags/6.1.1/includes/Ajax/Users.php#L227
- security@wordfencehttps://plugins.trac.wordpress.org/browser/kirki/tags/6.1.1/includes/HelperFunctions.php#L1098
- security@wordfencehttps://plugins.trac.wordpress.org/changeset?reponame=&old=3629933%40kirki&new=3629933%40kirki
- security@wordfencehttps://www.wordfence.com/threat-intel/vulnerabilities/id/fa1e0bcd-f881-4b01-b802-7cb18a22a07f?source=cve
Vendor Advisories for CVE-2026-18347(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 18× in last 7d / 18× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 13:00 UTCGHSA enrichment
- 2026-08-20 12:04 UTCEG score recompute
- 2026-08-20 12:04 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-19 13:29 UTCGHSA enrichment
- 2026-08-18 14:57 UTCEG score recompute
- 2026-08-18 14:56 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 16:20 UTCEG score recompute
- 2026-08-17 16:20 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 06:02 UTCEG score recompute
- 2026-08-17 06:02 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 07:29 UTCEG score recompute
- 2026-08-16 06:54 UTCEG score recompute
- 2026-08-16 06:54 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
- CVE-2013-3960EG 9.9CRITICAL
- CVE-2015-10143EG 9.8CRITICAL
- CVE-2016-11036EG 9.8CRITICAL
- CVE-2018-11541EG 9.8CRITICAL
- CVE-2011-4183NVD 6.5EG 9.8CRITICAL
- CVE-2018-10251EG 9.8EPSS p91CRITICAL
- CVE-2018-1217EG 9.8EPSS p99CRITICAL
- CVE-2018-0015EG 9.8CRITICAL
- CVE-2017-12582EG 9.8CRITICAL
- CVE-2017-1000056EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-18347?
When was CVE-2026-18347 disclosed?
Is CVE-2026-18347 actively exploited?
What is the CVSS score of CVE-2026-18347?
How do I remediate CVE-2026-18347?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-18347
Is Your Infrastructure Affected by CVE-2026-18347?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.