Security readout for executives and security teams
Plain-English summary
Older Magic Fields WordPress plugin versions could let an attacker run script in a user's browser through a plugin parameter. The main business risk is abuse of trusted WordPress sessions, especially administrators. The provided sources do not include a CVSS score or confirmed active exploitation.
Executive priority
Handle as a targeted WordPress plugin exposure issue. Prioritize sites where WordPress administrators manage sensitive content, customer data, or production operations. Urgency is moderate unless local evidence shows exposure or suspicious activity.
Technical view
CVE-2017-18610 is cross-site scripting in the Magic Fields plugin before 1.7.2 for WordPress. The reported vector is the custom-group-id parameter in RCCWP_CreateCustomFieldPage.php. The source bundle does not state whether the issue is stored or reflected, nor whether authentication is required.
Likely exposure
Exposure is likely limited to WordPress sites with the Magic Fields plugin installed below version 1.7.2. Sites not using this plugin are not affected based on the provided sources.
Exploitation context
The CVE is not listed in KEV, and the provided sources do not claim active exploitation. Public advisory information exists, so defenders should treat the issue as publicly known but not proven exploited from this bundle.
Researcher notes
The available record is sparse: no CVSS, CWE, exploit status, or detailed remediation text is provided. Analysis should stay anchored to the named plugin, version boundary, file, and parameter. Do not generalize this to unrelated WordPress plugins.
Mitigation direction
- Inventory WordPress sites for the Magic Fields plugin.
- Upgrade Magic Fields to 1.7.2 or later if available.
- If upgrade is unavailable, disable or remove the plugin.
- Review vendor plugin guidance before applying compensating controls.
- Restrict WordPress administrative access to trusted users.
Validation and detection
- Check installed Magic Fields versions across WordPress sites.
- Confirm no site runs Magic Fields before 1.7.2.
- Review WordPress access logs for suspicious plugin page requests.
- Verify plugin removal or upgrade in production.
- Document affected sites and remediation status.
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-18610 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/magic-fields/#developersCVE reference · x_refsource_MISC
- https://sumofpwn.nl/advisory/2016/cross_site_scripting_in_magic_fields_1_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.