Custom Css ProWordPress extension · Waspthemes
CVE-2019-5984
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-site request forgery (CSRF) vulnerability in Custom CSS Pro 1.0.3 and earlier allows remote attackers to hijack the authentication of administrators via unspecified vectors.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCross-site request forgery (CSRF) vulnerability in Custom CSS Pro WordPress plugin versions 1.0.3 and earlier allows remote attackers to perform unauthorized administrative actions by tricking authenticated administrators into visiting malicious pages or clicking crafted links, hijacking their session.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Custom Css ProWordPress extension
<= 1.0.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the Custom CSS Pro plugin filesAccess your WordPress installation via file manager or FTP. Navigate to /wp-content/plugins/ and look for a folder named 'custom-css-pro' or similar.Affected if The plugin folder does not exist, meaning the plugin is not installed and you are not affected.
-
Find the installed plugin versionOpen the plugin's main PHP file or the readme.txt file located in the plugin folder. Look for a version comment or the 'Version:' field in the file header.Affected if The version listed is 1.0.3 or lower.
-
Check version via WordPress adminLog in to WordPress admin panel, go to Plugins > Installed Plugins. Find 'Custom CSS Pro' in the list and read the version number displayed beneath the plugin name.Affected if The displayed version is 1.0.3 or earlier.
-
Verify the vulnerability conditionReview the affected version range provided: Waspthemes Custom CSS Pro versions 1.0.3 and earlier. If your installed version falls within this range and the plugin is active, the CSRF vulnerability is present.Affected if Your installed version is <= 1.0.3 and the plugin is currently active on your site.
You are affected if the Custom CSS Pro plugin by Waspthemes is installed and its version is 1.0.3 or lower, as this is the vulnerable version range for CVE-2019-5984.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Custom CSS Pro to a version newer than 1.0.3. As an interim measure, ensure administrators avoid clicking untrusted links and consider disabling the plugin until patched.
Fix this in Custom Css Pro
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5984 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-5984 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data