Security readout for executives and security teams
Plain-English summary
Custom CSS Pro for WordPress versions 1.0.3 and earlier has a CSRF issue that could let a remote attacker abuse an administrator's authenticated session. The public record does not provide CVSS scoring, exact vectors, active exploitation evidence, or a confirmed fixed version.
Executive priority
Treat this as a targeted WordPress hygiene issue, not an internet-wide emergency based on current evidence. Prioritize sites using the affected plugin, especially public business sites with frequent administrator access.
Technical view
CVE-2019-5984 describes a CSRF vulnerability in WaspThemes Custom CSS Pro 1.0.3 and earlier. The description says remote attackers may hijack administrator authentication through unspecified vectors. No CWE, CVSS, patch details, or exploit details are included in the provided sources.
Likely exposure
Exposure is limited to WordPress sites with Custom CSS Pro installed at version 1.0.3 or earlier. Risk is most relevant where administrators access the site from browsers that maintain active WordPress sessions.
Exploitation context
The bundle does not show CISA KEV listing or cited evidence of active exploitation. Because vectors are unspecified, assume attacker success may depend on an authenticated administrator interacting with malicious or attacker-controlled content.
Researcher notes
The public data is thin: affected product and version are clear, but vectors, CVSS, CWE, exploit maturity, and remediation are not. Further validation should focus on plugin presence, version, vendor status, and any site-specific administrative activity.
Mitigation direction
- Inventory WordPress sites for Custom CSS Pro and installed version.
- Check the WordPress plugin page and vendor guidance for fixed or maintained releases.
- Disable or remove the plugin if no supported fixed version is available.
- Restrict administrator access and avoid browsing untrusted sites while authenticated.
- Review administrator accounts and recent site changes for unexpected activity.
Validation and detection
- Confirm whether Custom CSS Pro is installed on each WordPress instance.
- Verify the plugin version is newer than 1.0.3, if a fixed release exists.
- Check public vendor and vulnerability records for updated remediation guidance.
- Review WordPress admin logs for suspicious plugin or CSS changes.
- Confirm no unexpected administrator sessions, accounts, or configuration changes exist.
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-2019-5984 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/custom-css-pro/CVE reference · x_refsource_MISC
- https://jvn.jp/en/jp/JVN29933378/index.htmlCVE reference · x_refsource_MISC
- https://wpvulndb.com/vulnerabilities/9439CVE 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.