LiveActive security incident?Get immediate response
CVE Record

CVE-2022-36417: WordPress 3D Tag Cloud plugin <= 3.8 - Multiple Stored Cross-Site Scripting (XSS) via Cross-Site Request Forgery (CSRF) vulnerability

Multiple Stored Cross-Site Scripting (XSS) via Cross-Site Request Forgery (CSRF) vulnerability in 3D Tag Cloud plugin <= 3.8 at WordPress.

MediumCVSS 6.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE affects WordPress sites using the 3D Tag Cloud plugin version 3.8 or earlier. A malicious site could trick an authenticated site user into saving harmful script content, creating stored XSS risk. The main concern is account/session impact and content manipulation, not direct server takeover.

Executive priority

Treat as a moderate-priority WordPress hygiene issue. Prioritize internet-facing or business-critical sites, especially where administrators frequently browse while logged in. Escalate only if the affected plugin is present and cannot be updated or removed quickly.

Technical view

CVE-2022-36417 is multiple stored XSS via CSRF in Vinoj Cardoza's 3D Tag Cloud WordPress plugin <=3.8. CVSS 3.1 is 6.1, with network access, low complexity, no attacker privileges, required user interaction, changed scope, and low confidentiality/integrity impact.

Likely exposure

Exposure is limited to WordPress installations with the 3D Tag Cloud plugin installed at version 3.8 or earlier. The source bundle does not identify other products, CPEs, or hosted service exposure.

Exploitation context

The bundle does not show CISA KEV listing or active exploitation evidence. The CVSS vector indicates exploitation requires user interaction, consistent with CSRF-driven stored XSS. Public sources cited here do not provide verified exploit activity details.

Researcher notes

The evidence supports affected product, version range, weakness classes, and CVSS details. It does not establish active exploitation or a specific fixed version. Validate remediation status against vendor or Patchstack data before making closure claims.

Mitigation direction

  • Inventory WordPress sites for the 3D Tag Cloud plugin and exact version.
  • Check Patchstack and the WordPress plugin page for vendor guidance or a fixed release.
  • Update the plugin if a maintained fixed version is available.
  • Disable and remove the plugin where no maintained fix is available.
  • Restrict WordPress admin access and review who can change plugin settings.

Validation and detection

  • Confirm whether any site runs 3D Tag Cloud version 3.8 or earlier.
  • Verify plugin status across production, staging, and archived WordPress instances.
  • Review plugin configuration and recent content changes for unexpected script-like content.
  • Check WordPress admin activity around plugin settings changes.
  • Document whether the plugin was updated, disabled, removed, or accepted as risk.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-36417 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.1 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.1CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.1Medium
CVSS 3.1 vector shape for CVE-2022-36417Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Vinoj Cardoza3D Tag Cloud (WordPress plugin)<= 3.8Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.