Security readout for executives and security teams
Plain-English summary
This CVE affects the wp-whois-domain WordPress plugin version 1.0.0. A website using it may reflect unsafe input into a page, allowing malicious JavaScript to run in a visitor’s browser if they are lured to a crafted request.
Executive priority
Treat this as a targeted WordPress plugin hygiene issue, not a confirmed emergency. Prioritize internet-facing sites and sites used by administrators or customers.
Technical view
CVE-2017-18612 is reflected cross-site scripting in wp-whois-domain 1.0.0 through the domain parameter in pages/func-whois.php. The bundle provides no CVSS score, CWE, patch version, or confirmed exploit activity.
Likely exposure
Exposure is limited to WordPress sites with the wp-whois-domain plugin, especially version 1.0.0, where the vulnerable plugin endpoint is reachable.
Exploitation context
The CVE is not listed in KEV, and the provided sources do not claim active exploitation. Reflected XSS generally requires a victim to open attacker-controlled content or links.
Researcher notes
Evidence is sparse: the CVE description identifies the vulnerable parameter and plugin version, but no score, affected CPE, fixed version, or exploitation confirmation is provided in the bundle.
Mitigation direction
- Inventory WordPress sites for the wp-whois-domain plugin and version 1.0.0.
- Disable or remove the plugin where it is not required.
- Check the WordPress plugin page and vendor guidance for maintained fixes or replacement options.
- Review web application firewall rules for generic reflected XSS protection.
- Monitor requests involving pages/func-whois.php and the domain parameter.
Validation and detection
- Confirm whether wp-whois-domain is installed on each WordPress instance.
- Verify the installed plugin version against the affected version, 1.0.0.
- Check whether pages/func-whois.php is publicly reachable.
- Review server and WAF logs for unusual domain parameter activity.
- Document any compensating controls and remaining public exposure.
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-18612 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/wp-whois-domain/#developersCVE reference · x_refsource_MISC
- https://rastating.github.io/wp-whois-domain-reflected-xss/CVE 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.