Security readout for executives and security teams
Plain-English summary
A logged-in WordPress user with Contributor privileges may upload arbitrary files through Templatiq 0.2.5 or earlier. This could seriously affect site confidentiality, integrity, and availability, especially if uploaded files become web-accessible or executable. The sources do not establish that code execution always follows.
Executive priority
Treat this as an urgent remediation item for affected sites because a low-privileged account may enable severe cross-scope impact. Prioritize internet-facing or business-critical WordPress systems and sites with multiple Contributors. Escalate immediately if suspicious uploads or account activity are found.
Technical view
CVE-2026-32474 is a CWE-434 arbitrary file upload vulnerability in wpWax Templatiq through version 0.2.5. Its CVSS 3.1 score is 9.9: network-accessible, low complexity, low privileges, no user interaction, changed scope, and high confidentiality, integrity, and availability impacts.
Likely exposure
Exposure is limited to WordPress installations running Templatiq 0.2.5 or earlier where an attacker controls a Contributor-level account. Unauthenticated exploitation is not supported by the supplied evidence. Publicly reachable administration or contribution workflows may increase practical risk.
Exploitation context
The supplied record is not in CISA KEV, and no cited source confirms active exploitation or a public exploit. Exploitation requires low-level authenticated access according to the description and CVSS vector. Exact upload paths, file handling behavior, and post-upload impact are not documented here.
Researcher notes
The evidence establishes an authenticated arbitrary file upload affecting versions through 0.2.5, but does not document the vulnerable endpoint, accepted file types, storage location, execution conditions, fixed version, or observed exploitation. Avoid assuming unauthenticated access or guaranteed remote code execution without additional vendor evidence.
Mitigation direction
- Identify every WordPress installation running Templatiq and record its installed version.
- Check wpWax and Patchstack guidance for a fixed release or vendor-approved mitigation.
- Disable or remove the plugin temporarily where business operations permit.
- Restrict or remove unnecessary Contributor-level accounts until remediation is confirmed.
- Preserve relevant logs before remediation if compromise is suspected.
Validation and detection
- Confirm the plugin is absent, disabled, or newer than the affected range after remediation.
- Review Contributor accounts for unknown, dormant, or unexpectedly privileged users.
- Inspect recent uploads for unexpected file types, locations, ownership, or modification times.
- Review WordPress and web-server logs for unusual authenticated upload activity.
- Run an integrity review of WordPress core, plugins, themes, and web-accessible upload directories.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-32474 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16PatchstackVulnerability scoring details
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/wordpress/plugin/templatiq/vulnerability/wordpress-templatiq-plugin-0-2-5-arbitrary-file-upload-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Unrestricted Upload of File with Dangerous Type
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.