dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-49344

HIGH · 7.1 CVSS v3.1 Published 2025-12-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
Cross-Site Request Forgery (CSRF) vulnerability in reneade SensitiveTagCloud sensitive-tag-cloud allows Stored XSS.This issue affects SensitiveTagCloud: from n/a through <= 1.4.1.

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 confidence

A CSRF vulnerability in the SensitiveTagCloud plugin enables attackers to inject malicious scripts that persist on the affected site (Stored XSS). By tricking authenticated administrators into visiting attacker-controlled pages, crafted requests can modify tag cloud configurations to include malicious JavaScript.

MitigationApply any available vendor patch immediately. If no patch exists, disable the plugin until a fix is released. For interim mitigation, ensure administrators avoid clicking untrusted links and consider implementing site-wide CSRF protections at the WAF/proxy level.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low

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

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 SensitiveTagCloud plugin is installed
    Navigate to WordPress admin dashboard > Plugins and locate 'SensitiveTagCloud' in the list of installed plugins. Note whether it appears as active or inactive.
    Affected if The plugin appears in the installed plugins list regardless of activation status.
  2. Identify the installed plugin version
    Click on the plugin to view its details, or inspect the plugin header in wp-content/plugins/sensitive-tag-cloud/sensitive-tag-cloud.php to read the 'Version' comment field. Compare this version number against any vendor advisories listing affected versions.
    Affected if No version number is listed, or the version falls within a range mentioned in official vulnerability references.
  3. Review tag cloud configuration for unexpected scripts
    Access the plugin settings page (typically under Settings > SensitiveTagCloud or a dedicated Tag Cloud admin menu). Inspect all tag cloud configurations, particularly fields that accept HTML or JavaScript (such as tag labels, tooltips, or CSS classes). Look for script tags, event handlers (onload, onclick, onerror), or encoded payloads.
    Affected if Any configuration field contains a script tag or suspicious JavaScript that was not intentionally added by an administrator.
  4. Inspect page source for stored XSS payloads
    View the source of pages displaying the tag cloud (typically the frontend of the site). Search for 'script', 'javascript:', 'onload=', 'onerror=', or similar patterns within the tag cloud HTML elements.
    Affected if Malicious script tags or event handlers appear in the rendered tag cloud markup.
  5. Check recent admin activity logs for configuration changes
    Review WordPress audit logs, plugin activity logs, or server access logs for POST requests to the plugin settings endpoint. Look for unusual timing or IP addresses associated with configuration saves.
    Affected if Configuration changes appear in logs that were not performed by known administrators.

Your environment is affected if the SensitiveTagCloud plugin is installed and its configuration contains unauthorized script injections or was modified without administrator knowledge.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply any available vendor patch immediately. If no patch exists, disable the plugin until a fix is released. For interim mitigation, ensure administrators avoid clicking untrusted links and consider implementing site-wide CSRF protections at the WAF/proxy level.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49344 — 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-2025-49344 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