{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4257 exists.","fix":"No fix has been published for CVE-2026-4257 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-4257 is a critical code injection vulnerability in supsysticcom Contact Form by Supsystic, published on 30 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-4257 and fix it if it is affected.\n\nWhat it is: CVE-2026-4257 is a critical code injection vulnerability in supsysticcom Contact Form by Supsystic, published on 30 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4257 exists.\n\nAffected product: supsysticcom Contact Form by Supsystic. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-4257/ (Markdown: https://insights.sbomify.com/CVE-2026-4257/index.md)","id":"CVE-2026-4257","markdown":"https://insights.sbomify.com/CVE-2026-4257/index.md","name":"CVE-2026-4257","record":{"aliases":["GHSA-fgcr-fh9h-2fw9"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can execute arbitrary code via Server-Side Template Injection in the Contact Form by Supsystic plugin.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"The Contact Form by Supsystic plugin for WordPress is vulnerable to Server-Side Template Injection (SSTI) leading to Remote Code Execution (RCE) in all versions up to, and including, 1.7.36. This is due to the plugin using the Twig `Twig_Loader_String` template engine without sandboxing, combined with the `cfsPreFill` prefill functionality that allows unauthenticated users to inject arbitrary Twig expressions into form field values via GET parameters. This makes it possible for unauthenticated attackers to execute arbitrary PHP functions and OS commands on the server by leveraging Twig's `registerUndefinedFilterCallback()` method to register arbitrary PHP callbacks.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2026-03-30","github_poc":3,"max_poc_stars":1,"metasploit":1,"nuclei":1,"refs":[{"date":"2026-07-09T08:02:12Z","kind":"github_poc","ref":"https://github.com/dann3xplo1t/CVE-2026-4257","stars":1,"title":"CVE-2026-4257 - Contact Form by Supsystic \u003c= 1.7.36 # SSTI to RCE "},{"date":"2026-03-30","kind":"metasploit","ref":"exploit/multi/http/wp_plugin_supsystic_contact_form_rce","stars":null,"title":"Supsystic Contact Form Wordpress Plugin SSTI RCE"},{"date":"2026-04-05T00:52:39Z","kind":"github_poc","ref":"https://github.com/bootstrapbool/cve-2026-4257","stars":0,"title":null},{"date":"2026-05-11T05:24:58Z","kind":"github_poc","ref":"https://github.com/shootcannon/CVE-2026-4257","stars":0,"title":"SSTI contact form to rce"},{"date":"2026-05-14","kind":"exploitdb","ref":"52564","stars":null,"title":"WordPress Plugin Supsystic Contact Form 1.7.36 - SSTI"},{"date":null,"kind":"nuclei","ref":"http/cves/2026/CVE-2026-4257.yaml","stars":null,"title":"WordPress Contact Form by Supsystic - Server-Side Template Injection"}],"tier":"weaponised"},"has_fix":null,"headline":"Contact Form by Supsystic \u003c= 1.7.36 - Unauthenticated Server-Side Template Injection via Prefill Functionality","id":"CVE-2026-4257","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"sjcl is missing point-on-curve validation in sjcl.ecc.basicKey.publicKey","id":"CVE-2026-4258"},"packages":[],"prev":{"headline":"LDAP Injection in PEAKUP's PassGate","id":"CVE-2026-4256"},"products":["Contact Form by Supsystic"],"published":"2026-03-30","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["supsysticcom"]},"summary":"Unauthenticated attackers can execute arbitrary code via Server-Side Template Injection in the Contact Form by Supsystic plugin.","url":"https://insights.sbomify.com/CVE-2026-4257/"}