Instant CssWordPress extension · Dylanblokhuis
CVE-2023-44243
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 Dylan Blokhuis Instant CSS plugin <= 1.2.1 versions.
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 the Instant CSS WordPress plugin allows remote attackers to induce authenticated users to perform unwanted actions (such as modifying plugin settings or injecting CSS) via crafted requests. The lack of proper CSRF token validation or SameSite cookie attributes on state-changing operations enables the attack.
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
Instant CssWordPress extension
<= 1.2.1CVSS 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.
-
Verify Instant CSS plugin is installedNavigate to WordPress admin > Plugins and locate 'Instant CSS' (also known as 'Instant CSS - Write CSS instantly' by Dylanblokhuis) in the list of installed pluginsAffected if The plugin appears in the installed plugins list and is activated
-
Confirm installed versionClick 'View Details' on the Instant CSS plugin in the WordPress plugins page to display the version number, or inspect the plugin file header in wp-content/plugins/instant-css/instant-css.phpAffected if The version number displayed is 1.2.1 or lower
-
Inspect plugin settings page for CSRF protectionAccess the plugin settings page (typically under Appearance > Instant CSS or Settings > Instant CSS) and view the page source (right-click > View Page Source) to search for 'wp_verify_nonce', 'wp_nonce', or 'nonce' in the forms that modify plugin settings or inject CSSAffected if Forms that save or update settings contain no nonce field or token parameter
-
Check SameSite cookie attributesOpen browser DevTools (F12) > Application tab > Cookies, then perform a state-changing action in the plugin (save settings, inject CSS). Inspect the cookies sent with the request to see if they have SameSite=Strict or SameSite=Lax attributesAffected if Cookies lack SameSite attribute or show SameSite=None without secure flag, and no anti-CSRF token is present in the request
A user is affected if the Instant CSS plugin (version 1.2.1 or lower) is installed and active, with state-changing forms lacking CSRF nonce tokens or cookies missing proper SameSite attributes.
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 dataImplement anti-CSRF tokens (nonces) for all state-changing operations and ensure cookies use SameSite=Strict or SameSite=Lax attributes to prevent cross-origin requests from being sent.
Fix this in Instant Css
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-44243 — 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-2023-44243 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