Security readout for executives and security teams
Plain-English summary
A WordPress contact-form plugin flaw can let an unauthenticated internet user run code on the web server. Public sources rate it critical because attack requires no login or user interaction. Organizations using Contact Form by Supsystic at version 1.7.36 or older should treat exposed sites as high priority.
Executive priority
Immediate action is warranted for any public WordPress site using this plugin. The business risk is potential server takeover, data theft, site defacement, or service disruption without requiring attacker credentials. Absence of confirmed active exploitation lowers certainty, not urgency.
Technical view
Contact Form by Supsystic <= 1.7.36 is vulnerable to unauthenticated server-side template injection in prefill handling. The plugin used Twig_Loader_String without sandboxing, allowing user-controlled GET parameter content to be interpreted as Twig expressions. The CVE description says this can lead to arbitrary PHP function and OS command execution. CWE-94, CVSS 9.8.
Likely exposure
Internet-facing WordPress sites running Contact Form by Supsystic versions up to and including 1.7.36 are the primary concern. Exposure is higher where public forms are reachable without authentication. The provided affected-product metadata is inconsistent, but the CVE title and description clearly identify <= 1.7.36 as vulnerable.
Exploitation context
No provided source or KEV listing indicates active exploitation. However, the vulnerability is network-reachable, unauthenticated, low-complexity, and can result in full confidentiality, integrity, and availability impact. Public code references and a WordPress repository changeset may help defenders validate, but they also increase urgency to patch quickly.
Researcher notes
The key issue is unsandboxed Twig string template evaluation reachable through cfsPreFill prefill functionality. Public references include the vulnerable code location and a WordPress changeset. Avoid assuming exploitation in the wild from severity alone. Validate exact deployed versions and compare against the repository fix history.
Mitigation direction
- Inventory WordPress sites for Contact Form by Supsystic installations.
- Update the plugin to a version newer than 1.7.36, if available.
- If no safe update is available, disable or remove the plugin.
- Check Supsystic, WordPress plugin repository, and Wordfence guidance for current remediation details.
- Prioritize externally exposed WordPress sites and high-value business web properties.
Validation and detection
- Confirm plugin version on each WordPress site.
- Verify vulnerable versions are upgraded beyond 1.7.36 or removed.
- Review web logs for unusual prefill-related query parameters.
- Investigate potentially affected servers for unauthorized file changes or processes.
- Confirm compensating controls do not replace applying the vendor fix.
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-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-4257 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.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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.
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:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/415c9658-bfb2-453b-a697-c63c08b0ca61?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/contact-form-by-supsystic/tags/1.7.36/modules/forms/views/forms.php#L323CVE reference
- https://plugins.trac.wordpress.org/changeset/3491826/contact-form-by-supsysticCVE reference
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.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.