LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1780: [CR]Paid Link Manager <= 0.5 - Reflected Cross-Site Scripting

The [CR]Paid Link Manager plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the URL path in all versions up to, and including, 0.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

MediumCVSS 6.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-1780 affects the [CR]Paid Link Manager WordPress plugin through version 0.5. A crafted link can cause malicious script to run in a victim’s browser if the victim clicks it. This is a phishing-assisted browser-side issue, not a server takeover by itself.

Executive priority

Handle during normal vulnerability management, but prioritize internet-facing WordPress sites and administrator-heavy workflows. The issue is not reported as actively exploited, but it can support phishing and account compromise if users are persuaded to click malicious links.

Technical view

The plugin has reflected cross-site scripting via the URL path, caused by insufficient input sanitization and output escaping. The CVSS 3.1 score is 6.1 with network attack vector, no privileges required, user interaction required, and changed scope. CWE-79 applies.

Likely exposure

Exposure is limited to WordPress sites with [CR]Paid Link Manager installed at version 0.5 or earlier. Public-facing sites are more likely targets because attackers can send crafted URLs to users or administrators.

Exploitation context

The source bundle does not indicate CISA KEV listing or active exploitation. Exploitation requires tricking a user into clicking a malicious link. Potential impact includes session-context script execution, content manipulation, or credential-phishing within the affected site’s browser context.

Researcher notes

Public details identify reflected XSS via URL path but do not provide a named patched version in the supplied sources. Avoid assuming remediation beyond vendor guidance. Validate exposure through plugin presence and version rather than WordPress core version.

Mitigation direction

  • Identify WordPress sites using [CR]Paid Link Manager.
  • If installed at version 0.5 or earlier, check vendor and WordPress plugin guidance.
  • Disable or remove the plugin if it is not business-critical.
  • Apply an updated fixed version if the vendor publishes one.
  • Use security controls that reduce reflected XSS risk where available.

Validation and detection

  • Inventory WordPress plugins across managed sites.
  • Confirm whether [CR]Paid Link Manager is installed.
  • Record the installed plugin version.
  • Treat version 0.5 or earlier as affected.
  • Review vendor, Wordfence, and WordPress plugin repository updates.
Prepared
Confidence
high
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-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-2026-1780 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-2026-1780Attack 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
silentwind[CR]Paid Link Manager0unaffected
Weakness

CWE details

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

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.