Security readout for executives and security teams
Plain-English summary
A WordPress plugin called trust-form version 2.0 exposed an XSS flaw in an admin edit page parameter. If a vulnerable site processes a crafted value, script could run in a browser viewing that admin page. The source bundle does not provide CVSS, patch status, or confirmed exploitation.
Executive priority
Prioritize as a targeted WordPress plugin hygiene issue, not a confirmed emergency. If trust-form 2.0 is present on externally managed or business-critical sites, schedule prompt removal, upgrade review, or compensating access controls. If absent, record non-exposure.
Technical view
CVE-2017-18613 describes cross-site scripting in the trust-form 2.0 WordPress plugin via the page parameter on wp-admin/admin.php?page=trust-form-edit. The bundle names no CVSS vector, CWE, fixed version, or affected CPEs. Treat scope as limited to confirmed trust-form 2.0 deployments unless vendor evidence expands it.
Likely exposure
Exposure is likely limited to WordPress sites that installed trust-form plugin 2.0. The vulnerable path is under wp-admin, so practical impact may depend on admin access, user interaction, or how WordPress routes the plugin page. The bundle does not confirm exposure for other versions.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. It only reports an XSS condition. Do not assume exploitation in the wild, a public weaponized exploit, or unauthenticated reachability without additional validated sources.
Researcher notes
Evidence is sparse: NVD-style metadata identifies the vulnerable parameter and plugin version but omits scoring, weakness classification, CPEs, and remediation details. Researchers should verify the original SumOfPwn advisory and WordPress plugin developer page before asserting affected ranges or fixes.
Mitigation direction
- Inventory WordPress sites for the trust-form plugin and installed version.
- Remove or disable trust-form if it is unused or unsupported.
- Check WordPress plugin and vendor guidance for fixed or safer versions.
- Restrict wp-admin access to trusted users and networks where feasible.
- Review admin accounts for unexpected changes after suspected exposure.
Validation and detection
- Confirm whether trust-form version 2.0 is installed on any WordPress property.
- Check whether wp-admin/plugin edit pages are reachable only by authorized administrators.
- Review plugin changelog or vendor advisory for fix status before upgrading.
- Look for suspicious admin-session activity around plugin management pages.
- Document findings because CVSS, CWE, and fixed-version evidence are incomplete.
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-18613 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://wordpress.org/plugins/trust-form/#developersCVE reference · x_refsource_MISC
- https://sumofpwn.nl/advisory/2016/cross_site_scripting_vulnerability_in_trust_form_wordpress_plugin.htmlCVE 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.