Skip to content
Founder-led WordPress incident response and care Request an assessment
3zerodigital Request a Website Assessment

Plugin security history

Single Sign On For TNG Vulnerability History & Security Timeline

The Wordfence Intelligence dataset currently contains 1 vulnerability records associated with Single Sign On For TNG, published between 2026 and 2026.

Dataset last synchronized: 2026-08-02 09:41:47 UTC

At a glance

Security Snapshot

1Total records
1Critical
0High
0Medium
0Low
0Informational
1Patched records
0Currently marked unpatched
2026-07-31First disclosure
2026-07-31Latest disclosure
1 of 1CVE coverage

Year-by-Year Timeline

YearRecordsRelative volume
202611 records

Severity Breakdown

SeverityRecordsShare
Critical1100%

Vulnerability-Type Breakdown

Privilege Escalation

1 record100%

First: 2026. Latest: 2026.

Patch Status

Patched
1
Currently marked unpatched
0
Unknown status
0

Patch status reflects the latest successfully synchronized source dataset and must be checked against the installed version.

Latest Known Patched Versions

  • 2.1.0

Affected-Version History

Ranges are deduplicated by source range record and shown with the associated disclosure and known patched versions.

Affected rangeVulnerabilityPublishedPatched versionSeverity
*-2.0.0Single Sign On For TNG <= 2.0.0 - Unauthenticated Privilege Escalation via Unverified Password ChangeJuly 31, 20262.1.0Critical

Selected source records

Latest Records

CriticalCVE-2026-15964

Single Sign On For TNG <= 2.0.0 - Unauthenticated Privilege Escalation via Unverified Password Change

Published: July 31, 2026

Affected versions
*-2.0.0
Patched versions
2.1.0
Original Wordfence record

Highest-Severity Records

CriticalCVE-2026-15964

Single Sign On For TNG <= 2.0.0 - Unauthenticated Privilege Escalation via Unverified Password Change

Published: July 31, 2026

Affected versions
*-2.0.0
Patched versions
2.1.0
Original Wordfence record

View all associated vulnerabilities

Need help reviewing an exposed WordPress website?

Running an affected version does not prove that a website was compromised. Suspicious redirects, unknown administrators, injected content, unexpected files or recurring malware may require a manual investigation.

Vulnerability data: Wordfence Intelligence. Analysis and practical guidance: 3Zero Digital.

Data Source, Attribution and Methodology

This page aggregates active Production Feed records. Counts are not software-quality rankings, and an affected version does not prove exploitation or infection. Read the full methodology.

Return to the Security History Directory