LiveActive security incident?Get immediate response
CVE Record

CVE-2025-46516: WordPress Twitter Card Generator plugin <= 1.0.5 - Cross Site Request Forgery (CSRF) to Stored XSS vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in silencecm Twitter Card Generator twitter-card-generator allows Stored XSS.This issue affects Twitter Card Generator: from n/a through <= 1.0.5.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A vulnerable WordPress plugin can let an attacker trick an authenticated site user into saving malicious script content. That script may later run for site visitors or administrators. The issue is rated high, but the supplied sources do not show active exploitation or a confirmed patch.

Executive priority

Treat as a high-priority WordPress plugin risk if the plugin is present. It does not justify emergency response without exposure, but affected internet-facing sites should be inventoried and remediated promptly once vendor guidance is confirmed.

Technical view

CVE-2025-46516 is a CWE-352 CSRF issue in silencecm Twitter Card Generator through version 1.0.5 that can lead to stored XSS. CVSS 3.1 is 7.1 with network attack vector, low complexity, no privileges required, user interaction required, and changed scope.

Likely exposure

Exposure is likely limited to WordPress sites with the Twitter Card Generator plugin installed at version 1.0.5 or earlier. The bundle does not provide CPEs, and version metadata is sparse, so asset inventory should confirm actual plugin presence.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation. Practical exploitation would require user interaction and a context where a targeted site user can be induced to trigger a state-changing action.

Researcher notes

Evidence supports CSRF leading to stored XSS, not standalone unauthenticated XSS. The supplied affected metadata is incomplete and no exploit details, patch version, or mitigation text are provided. Avoid expanding impact beyond the Patchstack and CVE descriptions.

Mitigation direction

  • Identify all WordPress sites using Twitter Card Generator.
  • Check vendor, WordPress plugin, and Patchstack guidance for a fixed version or mitigation.
  • If no supported fix exists, assess deactivation or replacement through change control.
  • Restrict administrative access and enforce anti-phishing controls for WordPress users.
  • Review stored plugin settings or generated content for unexpected script content.

Validation and detection

  • Inventory installed WordPress plugins and record Twitter Card Generator versions.
  • Confirm whether any installation is version 1.0.5 or earlier.
  • Review plugin changelogs or vendor advisories for remediation status.
  • Check administrative audit logs for unusual plugin setting changes.
  • Validate that relevant state-changing actions use CSRF protection.
Prepared
Confidence
medium
Sources
3

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
cve · low confidence lookup

CVE-2025-46516 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
High
CVSS
7.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:L

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
2Source 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
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2025-46516Attack 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:L

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
silencecmTwitter Card Generatortwitter-card-generator, 0unaffected
Weakness

CWE details

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

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.