CVE-2026-18438
Authenticated contributor can achieve RCE via filename validation bypass in Templately plugin.
Is CVE-2026-18438 being exploited?
Not confirmed. CVE-2026-18438 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.90% probability of exploitation in the next 30 days.
How severe is CVE-2026-18438?
CVE-2026-18438 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-18438?
Yes. A fix has been recorded for CVE-2026-18438. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-18438 affect?
CVE-2026-18438 affects WordPress Templately plugin (<=3.7.1), WordPress sites using Templately REST API endpoints (/templately/v1/*). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-18438?
Upgrade Templately to a fixed version >3.7.1 or disable/uninstall immediately; scan for webshells.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated (contributor+) can upload a crafted file via Templately REST API to achieve remote code execution and potential site takeover.
Immediate action required
- affected<= 3.7.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.