dbcve.org
3d Tag CloudWordPress extension · 3d Tag Cloud Project

CVE-2022-36417

MEDIUM · 6.1 CVSS v3.1 Published 2022-09-23
Fix available
A fix is available. Upgrade to after 3.8 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Multiple Stored Cross-Site Scripting (XSS) via Cross-Site Request Forgery (CSRF) vulnerability in 3D Tag Cloud plugin <= 3.8 at WordPress.

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 confidence

The 3D Tag Cloud WordPress plugin versions 3.8 and below contains multiple stored XSS vulnerabilities exploitable through CSRF. Attackers can inject malicious JavaScript into plugin settings by tricking authenticated administrators into submitting crafted requests, allowing script execution for all users viewing the affected pages.

MitigationUpdate the 3D Tag Cloud plugin to the latest patched version and implement CSRF tokens for all admin actions; temporarily disable the plugin if an update is unavailable.

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
3d Tag CloudWordPress extension
Affected:<= 3.8

CVSS 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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm 3D Tag Cloud plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or check for the /wp-content/plugins/3d-tag-cloud/ directory on the server
    Affected if The 3D Tag Cloud plugin directory exists in the WordPress installation
  2. Identify the installed version
    In WordPress admin, find the 3D Tag Cloud plugin in the Plugins list and read the version number under the plugin name, or inspect the plugin header in /wp-content/plugins/3d-tag-cloud/3d-tag-cloud.php
    Affected if The reported version is 3.8 or lower
  3. Review plugin settings for suspicious content
    Navigate to the plugin settings page (usually under Settings > 3D Tag Cloud) and inspect all input fields for unexpected script tags, iframe elements, or javascript: URIs
    Affected if Any settings contain JavaScript code or HTML script tags that were not intentionally configured by an administrator
  4. Check browser console for XSS errors on plugin admin page
    Load the 3D Tag Cloud settings page in a browser, open developer tools (F12), and check the Console tab for XSS-related error messages
    Affected if JavaScript errors appear indicating injected scripts are being executed when the settings page loads

A user is affected if the 3D Tag Cloud plugin version is 3.8 or lower and either malicious scripts are already present in plugin settings or the plugin is active without CSRF protection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 3.8
Interim mitigation

Update the 3D Tag Cloud plugin to the latest patched version and implement CSRF tokens for all admin actions; temporarily disable the plugin if an update is unavailable.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (version > 3.8)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find '3D Tag Cloud' plugin in the list
  4. Click 'Update Now' if an update is available, or manually download the latest version from wordpress.org and upload it

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in 3d Tag Cloud Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-36417 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-36417 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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