StreamWordPress extension · Xwp
CVE-2022-43490
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 XWP Stream plugin <= 3.9.2 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 XWP Stream plugin versions 3.9.2 and below allows attackers to trick authenticated users into unknowingly executing unwanted actions by forcing their browser to send malicious 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
StreamWordPress extension
<= 3.9.2CVSS 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 XWP Stream plugin installationCheck your WordPress installation at wp-content/plugins/ for a folder named 'xwp Stream' or similar. In the WordPress admin dashboard, navigate to Plugins > Installed Plugins and look for 'XWP Stream' in the list.Affected if The plugin folder exists or the plugin appears in the WordPress plugins list
-
Identify the installed version numberOpen the main plugin file (usually plugin.php or index.php inside the xwp-stream folder) and look for a version comment at the top, or check the readme.txt file for the 'Stable tag' entry. Alternatively, in WordPress admin, click on the plugin name to view its details which display the version.Affected if The displayed version number is 3.9.2 or lower
-
Confirm the plugin is activeIn WordPress admin under Plugins > Installed Plugins, verify that XWP Stream shows 'Active' status rather than 'Inactive' or 'Must Use'.Affected if The plugin is currently activated on the WordPress site
-
Understand the attack surfaceThis is a CSRF vulnerability that affects any state-changing action performed by the plugin (such as recording stream events, modifying settings, or other administrative functions). No specific feature toggle needs to be enabled for the flaw to exist.Affected if The plugin handles user-submitted data or performs administrative actions without requiring anti-CSRF nonce verification
Your environment is affected if XWP Stream plugin version 3.9.2 or lower is installed and active on your WordPress site, as the plugin lacks proper CSRF protection for state-changing operations.
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 (nonce verification) for state-changing operations and validate request origin via Referer header checks or SameSite cookie attributes.
Fix this in Stream
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43490 — 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-43490 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