Security readout for executives and security teams
Plain-English summary
WordPress sites using the formcraft3 plugin before version 3.4 may store unsafe script content in a form heading field. Stored XSS can affect people who later view the impacted form or admin content. The sources do not provide CVSS scoring, exploit details, or evidence of active exploitation.
Executive priority
Treat this as a targeted WordPress plugin hygiene issue, not a broad enterprise emergency. Prioritize internet-facing WordPress sites and any site where many users or administrators view forms.
Technical view
CVE-2017-18600 is a stored cross-site scripting issue in formcraft3 before 3.4 for WordPress, specifically via the New Form > Heading > Heading Text field. Public metadata does not specify attacker prerequisites, affected CPEs, CVSS, or detailed remediation beyond the vulnerable version boundary.
Likely exposure
Exposure is limited to WordPress installations with the formcraft3 plugin installed at a version earlier than 3.4. The source bundle does not identify other products or platforms.
Exploitation context
No CISA KEV listing is present, and the provided sources do not claim active exploitation. The public description confirms stored XSS but does not provide exploit maturity, required privileges, or real-world incident evidence.
Researcher notes
The record is sparse: no CVSS, CWE, CPE, prerequisites, or detailed patch note is included in the provided bundle. Analysis should remain bounded to formcraft3 before 3.4 and the named Heading Text stored XSS vector.
Mitigation direction
- Inventory WordPress sites for the formcraft3 plugin and installed version.
- Upgrade formcraft3 to version 3.4 or later where applicable.
- If upgrade status is unclear, check current vendor or plugin-maintainer guidance.
- Disable or remove the plugin where it is unused or cannot be updated.
- Review affected form heading content for unexpected script or markup.
Validation and detection
- Confirm whether formcraft3 is installed on each WordPress site.
- Verify the plugin version is not earlier than 3.4.
- Identify forms using Heading Text and review saved content.
- Check whether untrusted users can create or edit forms.
- Document findings and remediation status per site.
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.
CVE-2017-18600 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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 and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://wpvulndb.com/vulnerabilities/8877CVE reference · x_refsource_MISC
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.