Security readout for executives and security teams
Plain-English summary
CVE-2017-18611 is a cross-site scripting issue in the Magic Fields WordPress plugin before 1.7.2. The reported input is the custom-field-css parameter in RCCWP_CreateCustomFieldPage.php. Affected sites may expose administrators or users to injected script content if the vulnerable workflow is reachable.
Executive priority
Address during normal vulnerability remediation, with faster action for internet-facing or multi-user WordPress sites. No source in the bundle confirms active exploitation, but plugin XSS can still create account and content integrity risk.
Technical view
The CVE describes XSS in Magic Fields before 1.7.2 through insufficient handling of the custom-field-css parameter in RCCWP_CreateCustomFieldPage.php. The bundle provides no CVSS, CWE, authentication requirement, privilege requirement, or confirmed exploit chain, so exposure depends on plugin presence, version, and route accessibility.
Likely exposure
Likely limited to WordPress sites running the Magic Fields plugin earlier than 1.7.2. The source bundle does not identify affected CPEs, install counts, required privileges, or whether default configurations expose the vulnerable parameter.
Exploitation context
A public advisory is referenced, but the bundle does not show CISA KEV inclusion or any cited evidence of active exploitation. Treat this as a known historical WordPress plugin XSS issue rather than a confirmed currently exploited vulnerability.
Researcher notes
Key missing details are CVSS, authentication context, privileges needed, affected CPEs, and fixed-version evidence beyond the “before 1.7.2” wording. Do not assume broader WordPress impact; validate the specific plugin, version, and parameter handling.
Mitigation direction
- Inventory WordPress sites for the Magic Fields plugin and installed version.
- Upgrade Magic Fields to 1.7.2 or later where vendor guidance supports it.
- Disable or remove the plugin if it is unused or cannot be updated.
- Review the referenced advisory and plugin developer page for vendor-specific guidance.
- Prioritize sites with administrator access paths exposed to untrusted users.
Validation and detection
- Confirm no production site runs Magic Fields earlier than 1.7.2.
- Review plugin code or release notes for handling of custom-field-css.
- Check whether RCCWP_CreateCustomFieldPage.php is reachable by untrusted users.
- Use safe regression tests to verify the parameter is escaped before rendering.
- Review logs for suspicious activity around Magic Fields custom-field pages.
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-18611 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.