CVE-2022-41990 is a high severity (CVSS 7.1) cross-site request forgery flaw that allows stored XSS in the 3D Tag Cloud plugin for WordPress, versions up to and including 3.8. No official patch is listed, so remove the plugin or replace it.
What's affected
The record lists 3D Tag Cloud from Vinoj Cardoza, from the first release through 3.8. Patchstack states that no official patch is available. Patchstack gives the required privilege as none, so it is unauthenticated.
The record scores it 7.1 (High) with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L. Patchstack labels its own priority Low. The weakness class is CWE-352 (Cross-Site Request Forgery).
How to check if you're exposed
Start with an inventory. If you manage the site with WP-CLI, this lists every plugin with its version and whether an update is waiting:
wp plugin list --fields=name,status,version,update
Look for the folder cardoza-3d-tag-cloud. That folder name comes from the Patchstack entry for this issue, so confirm it matches what sits under wp-content on your site. Without WP-CLI, open the Plugins screen in the dashboard and read the version shown under the name. Version 3.8 or lower is affected.
Check staging copies, old multisite subsites and inactive plugins too. A deactivated plugin is still on disk, and some of these bugs are reachable through files that load even when the plugin is switched off, so deactivation alone is not a fix. Delete what you do not use. Because no patched release is known, the check ends with a removal decision, not an upgrade.
What to do now
- Decide whether you still need 3D Tag Cloud. If you can replace it with another plugin or a few lines of theme code, do that and remove it.
- Check pages and widgets that display the tag cloud for script content you did not add, and clean any you find.
- Review the site's user list and remove accounts you do not recognise.
- Turn on automatic updates for the plugin so the next fix lands without a ticket.
Why it matters
Cross-site request forgery means the plugin accepts a state changing request without confirming that the logged in user meant to send it. An attacker who gets an administrator to open a crafted page can have the browser send the request with the administrator's own session. Here the record says the forged request can store a script, which then runs in later visitors' browsers.
The two steps together are why the scope is rated changed and the score reaches 7.1. The forged request needs a victim to act, shown by the user interaction value in the vector, and then the stored script runs for everyone who views the affected output.
Patchstack lists no official patch and rates its own priority Low, probably because of the user interaction requirement and the plugin's small footprint. An unpatched plugin with a stored script route is still not worth keeping for a decorative tag cloud. The record's KEV flag is false, and nothing I fetched reports exploitation in the wild.
Quick check
What is stored XSS in simple terms?
A malicious script gets saved by the site and then runs in the browser of anyone who loads the affected page, which can lead to stolen sessions or changed content.
Is there a safe version?
Patchstack lists no official patch. Remove the plugin or replace it with a maintained alternative.
Sources
Safeguard can help you see this across many sites or repositories at once. Paste a manifest into the free in-browser dependency scan at gold.safeguard.sh/scan or look the issue up in the Gold directory to see how the record is tracked.
Last reviewed: 19 October 2026.