StylistWordPress extension · Stylist Project
CVE-2022-47183
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 StylistWP Extra Block Design, Style, CSS for ANY Gutenberg Blocks plugin <= 0.2.6 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 StylistWP Extra Block Design, Style, CSS for ANY Gutenberg Blocks WordPress plugin affecting versions 0.2.6 and below. The vulnerability allows attackers to trick authenticated administrators into unknowingly executing unwanted actions via maliciously crafted requests.
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
StylistWordPress extension
<= 0.2.6CVSS 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 StylistWP plugin installationCheck the wp-content/plugins directory for a folder named 'stylistwp-extra-block-design' or similar Stylist-related folderAffected if The plugin folder exists in the plugins directory
-
Identify the installed versionOpen the plugin's main PHP file and locate the version comment in the file header, or check the readme.txt file for the Version fieldAffected if The version number found is 0.2.6 or lower
-
Confirm plugin activation statusIn the WordPress admin dashboard, go to Plugins > Installed Plugins and verify if StylistWP Extra Block Design is activated, or query the wp_options table for the active_plugins optionAffected if The plugin is currently active in the WordPress installation
-
Verify the CSRF vulnerability conditionThis is a CSRF flaw requiring administrator interaction. The vulnerability exists when the plugin handles form submissions or AJAX requests without proper nonce validation on state-changing actionsAffected if The plugin is active, running version 0.2.6 or below, and administrators can be tricked into submitting malicious requests
You are affected if the StylistWP Extra Block Design plugin is installed, activated, and running version 0.2.6 or lower
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 the plugin to a version newer than 0.2.6 when available. As an interim measure, disable the plugin if not essential. The fix requires implementing proper nonce validation on all state-changing form submissions and AJAX requests within the plugin.
Fix this in Stylist
Scoped from the published advisory
- Consultation3.0 h
- Implementation5.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47183 — 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-2022-47183 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