Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as WordPress administrator
-
DeliveryInject template syntax into form editor
-
ExploitStored content reaches unsandboxed engine
-
ExecutionTemplate compiled and executed on page load
-
ImpactExecute arbitrary code / leak salts and DB credentials
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires WordPress administrator privileges to place template-injection content into the Supsystic contact-form editor on a site running the plugin before version 1.11.1, where the template engine is not sandboxed. The limiting factor is that only an administrator can store the payload (PR:H), so direct exploitation depends on holding or compromising an admin account; however, once the payload is stored, no authentication or user interaction is needed for the secondary effect - any unauthenticated visitor loading a page that contains the form causes the template to compile and execute, exposing server-side secrets such as authentication salts and database credentials. |
| Impact | Signals point to a real but gated issue rather than a drop-everything emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N, C:H/I:H/A:H, 7.2 High) describes a network-reachable, low-complexity flaw whose only brake is PR:H - an attacker must first hold WordPress administrator rights to store the malicious template. SSVC agrees on the gravity of impact (Technical Impact: total) while tempering urgency: Exploitation 'none' (no observed activity) and Automatable 'no' (admin access must be obtained per target). KEV status is NO, so there is no confirmed active exploitation. The vuln.today Decision label is 'this_week', consistent with a serious code-execution flaw that is not yet weaponized. EPSS is not provided in the input, so exploitation probability cannot be quantified here. One important nuance from the description partially conflicts with the PR:H framing: although injecting the payload requires an administrator, the stored template is compiled and executed for ANY visitor who loads the form page, meaning the secondary information-disclosure effect (reading auth salts and DB credentials) is reachable by an unauthenticated visitor once an admin - malicious, coerced, or compromised - has planted the payload. This makes the flaw more dangerous in multi-admin, agency, or compromised-credential scenarios than PR:H alone suggests. Net: a genuine high-impact RCE worth patching promptly, but the administrator precondition keys it below internet-facing unauthenticated bugs in triage. |
| Exploit ScenarioDerived | An attacker who holds (or has phished/compromised) WordPress administrator access opens the Supsystic contact-form editor and stores server-side template injection syntax as form content; because the template engine is not sandboxed, that content is compiled and executed as code when the form renders, yielding arbitrary code execution on the server. Thereafter, every unauthenticated visitor who loads a page containing the form triggers the payload, allowing exfiltration of server-side secrets such as authentication salts and database credentials. A public PoC reference exists (WPScan); it is not verified as working exploit code. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 29, 2026
Stored server-side template injection in the WordPress plugin Contact Form by Supsystic before 1.11.1 lets a WordPress administrator place template code into form-editor content that the unsandboxed template engine later compiles and runs when any visitor loads a page containing the form. The direct injection path is gated by administrator privileges (PR:H), but once the payload is stored the secondary effect needs no authentication or interaction and can expose server-side secrets such as authentication salts and database credentials. A public PoC reference exists; it is not verified as working exploit code, and no confirmed active exploitation or CISA KEV entry is present, though the issue is prioritized for this week.
RemediationAI
Vendor-released patch: upgrade Contact Form by Supsystic to 1.11.1 or later; the patch is available from the vendor per the WPScan advisory at https://wpscan.com/vulnerability/15274345-5ad4-456f-9b5e-40d575ecb272/. The available sources do not describe a separate workaround, so the 1.11.1 update is the complete fix indicated by the data. The CVE record at https://nvd.nist.gov/vuln/detail/CVE-2026-115301 provides the authoritative reference.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is a WordPress contact-form plugin whose form-editor content is passed into a template engine for rendering. Because that engine is not sandboxed, stored content can be interpreted as executable template syntax, placing the issue in CWE-94 (code injection) rather than a simple cross-site scripting flaw. The injected template is compiled and executed at page render time, so any visitor loading a page with the form triggers execution; this is why an unauthenticated visitor can observe the secondary impact even though storing the payload requires administrator access. CPE data identifies the affected package generically as contact_form_by_supsystic before 1.11.1, and EUVD lists the range as Contact Form by Supsystic 0 <1.11.1.
Know when Contact Form By Supsystic gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Admin must store the payload (PR:H) over the network with no interaction (AV:N/UI:N/AC:L); unsandboxed template execution yields full code execution on one system, so C:H/I:H/A:H and S:U.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
3DescriptionCVE.org
The Contact Form by Supsystic WordPress plugin before 1.11.1 does not sandbox the template engine used to render its forms and allows stored form-editor content to reach that engine as executable template code, enabling an administrator to perform server-side template injection and execute arbitrary code on the server. The injected template is compiled and executed whenever any visitor loads a page containing the form, so the stored payload also lets an unauthenticated visitor read server-side secrets such as authentication salts and database credentials.
Technical POC Analysis
The bug class is code injection (CWE-94), specifically stored server-side template injection.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
The Contact Form by Supsystic plugin for WordPress (versions before 1.11.1) contains a high-severity stored template injection flaw that requires administrator access to exploit initially, but can lead to unauthenticated exposure of critical server secrets once a malicious form is saved. This puts organizations using the plugin at risk of data breaches involving authentication salts and database credentials, potentially compromising the entire WordPress instance. Leadership should prioritize patching within the week due to the sensitive data exposure and the availability of a public proof-of-concept reference.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
More in Contact Form By Supsystic
View allRemote code execution in Contact Form by Supsystic plugin for WordPress (all versions ≤1.7.36) allows unauthenticated at
Cross-site request forgery in the Supsystic Contact Form plugin for WordPress before 1.11.1 lets an attacker overwrite a
Unauthenticated deletion of stored form statistics is possible in the Contact Form by Supsystic WordPress plugin before
Cross-site request forgery in the WordPress plugin Contact Form by Supsystic before 1.11.1 lets an attacker permanently
Email header injection in the Supsystic Contact Form plugin for WordPress (versions before 1.11.1) lets unauthenticated
Stored cross-site scripting in the Contact Form by Supsystic WordPress plugin before 1.8.0 lets users with access to the
Unauthenticated information disclosure in the Supsystic Contact Form WordPress plugin (all versions through 1.10.5) lets
Stored cross-site scripting in the Contact Form by Supsystic WordPress plugin (all versions ≤1.10.2) allows unauthentica
Unauthenticated cross-site scripting in Contact Form by Supsystic WordPress plugin (all versions before 1.10.0) allows a
Unauthenticated authentication bypass in the Contact Form by Supsystic WordPress plugin (versions before 1.10.0) exposes
Missing authorization (CWE-862) in the WordPress plugin Contact Form by Supsystic, affecting all versions through 1.10.7
EUVD-2026-112610
GHSA-vw93-qjx2-fxhw
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB