{"id":"CVE-2026-104246","kind":"vulnerability","aliases":["CVE-2026-104246"],"related":[],"title":"WordPress Contact Form 7 Signature Addon: path traversal attaches server files to email","description":"The Contact Form 7 Signature Addon WordPress plugin through 4.2.2 does not sanitize a signature field value before building an email attachment path from it, allowing unauthenticated users to attach arbitrary files (bounded to wp-content on current Contact Form 7) to a form's outgoing email via path traversal; when a form is configured to email a copy to a submitter-controlled address, the attacker can read the targeted file.","summary":"The Contact Form 7 Signature Addon WordPress plugin through 4.2.2 builds an email attachment path from an unsanitized signature field, so an unauthenticated visitor can traverse directories. On current Contact Form 7 the attacker can attach files under wp-content and, where the form emails a copy to the submitter, read the targeted file.","severity":"medium","cvss":5.9,"epss":null,"exploited":false,"exploited_at":null,"products":[],"ecosystems":[],"tags":["contact-form-7","package","self-hosted","wordpress"],"not_affected_if":["no-signature-addon","no-submitter-copy-email","plugin-updated"],"how_to_check":"- Check the installed version of the Contact Form 7 Signature Addon plugin in the WordPress admin plugin list or `wp plugin list --name=<plugin-slug>`\n- Look for forms that use a signature field and are set to email a copy to the submitter\n- unknown","fix":"- Update the Contact Form 7 Signature Addon plugin to a version later than `4.2.2`; the sources do not name the fixed version\n- Until updated, disable the Signature Addon plugin or remove the signature field from public forms","status":"open","published_at":"2026-10-17T06:16:33+00:00","first_seen_at":"2026-10-23T21:57:14+00:00","triaged_at":"2026-10-25T04:08:55+00:00","updated_at":"2026-10-25T04:08:55+00:00","category":"package","confidence":0.7,"triage":{"at":"2026-10-25T04:08:55Z","model":"claude-haiku-5-5","output":{"fix":"- Update the Contact Form 7 Signature Addon plugin to a version later than `4.2.2`; the sources do not name the fixed version\n- Until updated, disable the Signature Addon plugin or remove the signature field from public forms","reach":"internet","title":"WordPress Contact Form 7 Signature Addon: path traversal attaches server files to email","impact":"medium","summary":"The Contact Form 7 Signature Addon WordPress plugin through 4.2.2 builds an email attachment path from an unsanitized signature field, so an unauthenticated visitor can traverse directories. On current Contact Form 7 the attacker can attach files under wp-content and, where the form emails a copy to the submitter, read the targeted file.","category":"package","nicknames":[],"who_cares":["wordpress","contact-form-7","self-hosted"],"confidence":0.7,"needs_auth":"no","worst_case":"Unauthenticated attacker reads files under wp-content, such as configuration files","analyst_note":"Confirm the fixed plugin version and check the NVD entry at https://nvd.nist.gov/vuln/detail/CVE-2026-104246 for the exact affected range and any vendor advisory.","how_to_check":"- Check the installed version of the Contact Form 7 Signature Addon plugin in the WordPress admin plugin list or `wp plugin list --name=<plugin-slug>`\n- Look for forms that use a signature field and are set to email a copy to the submitter\n- unknown","needs_analyst":true,"not_affected_if":["no-signature-addon","no-submitter-copy-email","plugin-updated"],"who_is_affected":"Sites running the Contact Form 7 Signature Addon plugin through version 4.2.2 with a form that includes a signature field and is configured to email a copy to a submitter-controlled address. The sources say the attachment is bounded to wp-content on current Contact Form 7, so sites without the addon or without that email setting are not exposed in the described way.","user_interaction":"no","needs_special_setup":"yes","severity_if_unknown":"medium"},"cost_usd":0.000693,"input_tokens":3362,"output_tokens":713,"severity_before":"medium"},"analyst_status":null,"analyst_note":null,"search":"'-104246':16A,19A '-2026':15A,18A '4.2.2':38B,93C '7':4A,23B,32B,60B,87C,125C 'addon':6A,34B,89C 'address':149C 'allow':109C 'arbitrari':114C 'attach':9A,42B,64B,105C,113C 'attack':62B,151C 'bound':116C 'build':39B,102C 'configur':139C 'contact':2A,21B,30B,58B,85C,123C 'contact-form':20B 'content':69B,120C 'control':148C 'copi':76B,143C 'current':57B,122C 'cve':14A,17A 'directori':55B 'email':13A,41B,74B,104C,131C,141C 'field':48B,99C 'file':11A,65B,83B,115C,156C 'form':3A,22B,31B,59B,73B,86C,124C,128C,137C 'host':27B 'outgo':130C 'packag':24B 'path':7A,43B,106C,133C 'plugin':36B,91C 'read':80B,153C 'sanit':96C 'self':26B 'self-host':25B 'server':10A 'signatur':5A,33B,47B,88C,98C 'submitt':79B,147C 'submitter-control':146C 'target':82B,155C 'travers':8A,54B,134C 'unauthent':51B,110C 'unsanit':46B 'user':111C 'valu':100C 'via':132C 'visitor':52B 'wordpress':1A,28B,35B,90C 'wp':68B,119C 'wp-content':67B,118C","nicknames":[],"mitigations":[],"who_affected":"Sites running the Contact Form 7 Signature Addon plugin through version 4.2.2 with a form that includes a signature field and is configured to email a copy to a submitter-controlled address. The sources say the attachment is bounded to wp-content on current Contact Form 7, so sites without the addon or without that email setting are not exposed in the described way.","tier":"C","verified":{},"analyst_revisit_at":null,"first_public_at":"2026-10-17T06:16:33+00:00","kev":null,"cvss_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","cvss_by":"134c704f-9b21-4f2e-91b3-4a467353bcc0","poc_count":0,"sources":[{"source":"nvd","external_id":"CVE-2026-104246","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-104246","severity":null,"published_at":"2026-10-17T06:16:33+00:00","modified_at":"2026-10-19T21:02:51+00:00","first_seen_at":"2026-10-23T21:57:14+00:00","fetched_at":"2026-10-23T22:28:55+00:00","note":null}],"documents":[],"notice":"Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai"}