Security readout for executives and security teams
Plain-English summary
A WordPress contact form plugin can reflect unsafe input back into a page. An attacker could send a crafted link that runs script in the victim’s browser if clicked. This can support phishing, session-related abuse, or content manipulation within the affected site context.
Executive priority
Treat as a high-priority web risk for WordPress sites using this plugin. Prioritize public websites, administrator-facing workflows, and sites handling customer interactions. If the plugin is not installed, no action is needed beyond normal monitoring.
Technical view
CVE-2026-0753 is reflected XSS in Super Simple Contact Form through the sscf_name parameter in versions up to and including 1.6.2. Sources attribute it to insufficient input sanitization and output escaping. It is unauthenticated and network-reachable, but requires a user interaction such as following a malicious link.
Likely exposure
Exposure is limited to WordPress sites running Super Simple Contact Form at version 1.6.2 or earlier, especially where the form is publicly reachable. Sites not using this plugin are not affected based on the provided sources.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. The practical risk is social engineering: attackers must get a target to open a crafted URL. Impact increases if the target is an authenticated site administrator.
Researcher notes
The provided record identifies CWE-79 and references WordPress Trac locations around line 152 for version 1.6.2 and trunk. The affected metadata is inconsistent, listing default unaffected while the description says all versions up to 1.6.2. No source in the bundle names a fixed version.
Mitigation direction
- Inventory WordPress sites for Super Simple Contact Form installations.
- Check the installed plugin version against 1.6.2 or earlier.
- Review the plugin’s WordPress.org page and vendor guidance for an updated fixed version.
- If no fix is available, disable or remove the plugin where business impact permits.
- Apply standard WordPress hardening and limit administrator exposure to untrusted links.
Validation and detection
- Confirm whether the plugin is installed on production WordPress sites.
- Record installed version and compare to affected versions up to 1.6.2.
- Review web access logs for suspicious requests containing the sscf_name parameter.
- Validate remediation in staging before re-enabling affected forms.
- Confirm no affected plugin copies remain in inactive WordPress 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-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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 lookupCVE-2026-0753 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
- High
- CVSS
- 7.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
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:C/C:L/I:L/A:N3.92.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/e10c0d8d-718d-45dd-9ac3-a2673a6a16af?source=cveCVE reference
- https://downloads.wordpress.org/plugin/super-simple-contact-form.1.6.2.zipCVE reference
- https://wordpress.org/plugins/super-simple-contact-form/CVE reference
- https://plugins.trac.wordpress.org/browser/super-simple-contact-form/trunk/super-simple-contact-form.php#L152CVE reference
- https://plugins.trac.wordpress.org/browser/super-simple-contact-form/tags/1.6.2/super-simple-contact-form.php#L152CVE 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 Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
