WordPress TrustedLogin Connector plugin <= 2.0.3 - Sensitive Data Exposure vulnerability

Why this deserves its current priority

CVSS is 5.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps TrustedLogin/TrustedLogin Connector (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for TrustedLogin/TrustedLogin Connector.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Sep 23, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 23, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 23, 2026

Sources and claim methodology

• Source referencepatchstack.com

Related CVEs

• Automation-controller: automation-controller: unauthenticated /api/v2/ping/ discloses automation-mesh instance topology and instance-group membershipAlso CWE-497
• RabbitMQ: Stream protocol skips per vhost per user connection limitsSame generic ecosystem
• RabbitMQ: Monitoring-tag DELETE of auth-attempt metricsSame generic ecosystem
• RabbitMQ: CORS * reflects Origin with Allow-CredentialsSame generic ecosystem
• RabbitMQ: Atom table exhaustion via stream `chunk_selector`Same generic ecosystem
• RabbitMQ: Cross-vhost quorum-queue status and stream tracking disclosureSame generic ecosystem