Cardoza 3d Tag CloudWordPress extension · Cardozatechnologies
CVE-2022-41990
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 Vinoj Cardoza 3D Tag Cloud allows Stored XSS.This issue affects 3D Tag Cloud: from n/a through 3.8.
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 · high confidenceCross-Site Request Forgery (CSRF) vulnerability in the Vinoj Cardoza 3D Tag Cloud WordPress plugin allows attackers to craft malicious requests that inject Stored XSS payloads. The lack of anti-CSRF tokens on state-changing operations enables authenticated administrators to be tricked into submitting forged requests that persist malicious scripts.
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
Cardoza 3d Tag CloudWordPress extension
<= 3.8CVSS 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 plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder containing '3d-tag-cloud', 'cardoza-3d-tag-cloud', or similar naming patterns. Alternatively, query the wp_options table for option_name = 'active_plugins' and check if the plugin appears in the list.Affected if The plugin folder exists in wp-content/plugins/ and the plugin is active in WordPress.
-
Determine installed versionOpen the main plugin PHP file (usually named similar to the folder) and look at the plugin header comment for 'Version: X.X' or check the readme.txt file in the plugin folder for the 'Stable tag' entry.Affected if The version number is 3.8 or lower.
-
Inspect admin forms for CSRF protectionNavigate to the plugin settings page in the WordPress admin panel. View the page source (or examine the plugin's admin PHP files) and look for hidden form fields containing nonce values such as wp_nonce_field, _wpnonce, or check_admin_referer calls.Affected if State-changing forms (such as saving tag settings, adding/editing tags) lack nonce token fields or nonce verification in the form handling code.
-
Verify tag data handlingExamine the plugin code that processes and saves tag data (search for $_POST or $_GET handling related to tags). Check if input validation and output escaping (such as esc_html, esc_attr, or sanitize_text_field) are applied to user-supplied tag content.Affected if User-supplied tag data is stored without sanitization and displayed without proper output escaping, allowing stored XSS.
You are affected if the Cardozatechnologies Cardoza 3d Tag Cloud plugin is active on your WordPress site and is version 3.8 or lower, with admin forms lacking CSRF nonce protection.
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) on all form submissions and AJAX actions; add proper input validation and output escaping on all user-supplied tag data before storage and display.
Fix this in Cardoza 3d Tag Cloud
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41990 — 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-41990 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