The Themify Builder plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 7.7.7. 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 subscriber-level access and above, to overwrite or delete the generated CSS stylesheet file of arbitrary posts, including private and draft posts owned by other users, and modify plugin-scoped font options. The required CSRF nonce (tf_nonce) is emitted on public front-end builder pages via wp_localize_script, making it trivially obtainable by any authenticated user visiting such a page.
CVE-2026-15407
MEDIUMPre-NVD 4.34.3—Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
Score 4.3 from GitHub Security Advisory published 2026-07-16. a secondary CVSS source baseline 4.3; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
4.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.3Exploit: NoneExposed: 0
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)
- EPSS
- 20.8%
- KEV
- Not listed
Published
July 16, 2026
Last Modified
July 18, 2026
References (10)
- security@wordfencehttps://plugins.trac.wordpress.org/browser/themify-builder/tags/7.7.5/classes/class-themify-builder-stylesheet.php#L160
- security@wordfencehttps://plugins.trac.wordpress.org/browser/themify-builder/tags/7.7.5/classes/class-themify-builder-stylesheet.php#L17
- security@wordfencehttps://plugins.trac.wordpress.org/browser/themify-builder/tags/7.7.5/classes/class-themify-builder-stylesheet.php#L313
- security@wordfencehttps://plugins.trac.wordpress.org/browser/themify-builder/tags/7.7.5/classes/class-themify-builder-stylesheet.php#L69
- security@wordfencehttps://plugins.trac.wordpress.org/browser/themify-builder/tags/7.7.7/classes/class-themify-builder-stylesheet.php#L160
- security@wordfencehttps://plugins.trac.wordpress.org/browser/themify-builder/tags/7.7.7/classes/class-themify-builder-stylesheet.php#L17
- security@wordfencehttps://plugins.trac.wordpress.org/browser/themify-builder/tags/7.7.7/classes/class-themify-builder-stylesheet.php#L313
- security@wordfencehttps://plugins.trac.wordpress.org/browser/themify-builder/tags/7.7.7/classes/class-themify-builder-stylesheet.php#L69
- security@wordfencehttps://plugins.trac.wordpress.org/changeset?reponame=&old=3607906%40themify-builder&new=3607906%40themify-builder
- security@wordfencehttps://www.wordfence.com/threat-intel/vulnerabilities/id/b59e2773-31f0-4c19-b066-30982761bc44?source=cve
Vendor Advisories for CVE-2026-15407(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 12× in last 7d / 12× 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-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 02:35 UTCEG score recompute
- 2026-07-19 02:35 UTCGHSA enrichment
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 07:04 UTCEG score recompute
- 2026-07-17 07:04 UTCGHSA enrichment
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-16 08:40 UTCEG score recompute
- 2026-07-16 08:39 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
Frequently asked(5)
What is CVE-2026-15407?
CVE-2026-15407 is a medium vulnerability published on July 16, 2026. The Themify Builder plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 7.7.7. 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 subscriber-level…
When was CVE-2026-15407 disclosed?
CVE-2026-15407 was first published in the National Vulnerability Database on July 16, 2026, with the most recent update on July 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15407 actively exploited?
CVE-2026-15407 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-15407?
CVE-2026-15407 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-15407?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15407, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-15407
Is Your Infrastructure Affected by CVE-2026-15407?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.