Is Single Sign On For TNG safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (2.2.0). As of 2026-11-04. 2 issues are on record for older versions; version 2.2.0 or newer fixes all of them that state a fix. Keep Single Sign On For TNG on the latest version (2.2.0) and remove it if you do not use it.

Which versions of Single Sign On For TNG are vulnerable?

Known issues on record (newest first): Authentication bypass (older than 2.2.0, fixed in 2.2.0); Authentication bypass (2.0.0 and older, fixed in 2.1.0). The full list with sources is on this page.

What is the latest version of Single Sign On For TNG?

2.2.0, according to wordpress.org (last updated 2026-08-29). It has 20+ active installs.

What should I do if my Single Sign On For TNG is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update single-sign-on-for-tng). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · single-sign-on-for-tng · data as of 2026-11-04

Is Single Sign On For TNG safe? Known vulnerabilities and latest version

Latest version: 2.2.0
Last updated: 2026-08-29
Active installs: 20+
Known issues on record: 2
Unpatched in latest: 0
Tested up to WP: 7.1.4 · PHP 7.0+

Single Sign On For TNG automates the login to the genealogy program TNG by Darrin Lithgoe. — by Colin Stearman

What to do

Update to the latest version (2.2.0). Anything older than 2.2.0 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get single-sign-on-for-tng --field=version shows what you run; wp plugin update single-sign-on-for-tng updates it.

Check your version

Known vulnerabilities

2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

critical 9.8 CVE-2026-16299 · published 2026-08-10

Authentication bypass in Single Sign On For TNG (older than 2.2.0)

Affected: older than 2.2.0
Fixed in: 2.2.0
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by CISA ADP

Details from the advisory

The Single Sign On For TNG WordPress plugin before 2.2.0 does not properly validate a password reset request, allowing unauthenticated attackers to reset the password of arbitrary users, including administrators, which could lead to a full site takeover.

NVD CVE-2026-16299 WPScan advisory

critical 9.8 CVE-2026-15964 · published 2026-08-01

Authentication bypass in Single Sign On For TNG (2.0.0 and older)

Affected: 2.0.0 and older
Fixed in: 2.1.0 *
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The Single Sign On For TNG plugin for WordPress is vulnerable to Authentication Bypass via unauthenticated password reset in all versions up to, and including, 2.0.0. This is due to the `ssoprocess_ajax()` function — registered on `wp_ajax_nopriv_ssoprocess_ajax` and therefore reachable without authentication — accepting an attacker-supplied `email` parameter with the `setnewpassword` operation and calling `reset_password()` on the resolved account without any ownership token, email confirmation link, or capability check. The sole guard is a call to `check_ajax_referer()`, which provides no authorization barrier because the `ssoajaxnonce` nonce is publicly broadcast on every front-end page via `wp_localize_script()` into the `SSOPWDREQUIREMENT` JavaScript object; since WordPress computes nonces for logged-out visitors against a shared anonymous session context, any unauthenticated visitor can scrape a valid nonce from the homepage and use it to authenticate the request. This makes it possible for unauthenticated attackers to change the password of any WordPress account, including administrator accounts, enabling complete site takeover.

NVD CVE-2026-15964 Wordfence advisory Code change (fix)Plugin source

Recent activity

2026-08-29 — latest release on wordpress.org (2.2.0).
2026-08-10 — Authentication bypass disclosed (CVE-2026-16299), fixed in 2.2.0.
2026-08-01 — Authentication bypass disclosed (CVE-2026-15964), fixed in 2.1.0.

Free. We check the CVE feeds every day and email you only when a new issue for Single Sign On For TNG (single-sign-on-for-tng) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Authentication bypass (2)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/single-sign-on-for-tng (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/single-sign-on-for-tng"><img src="https://laskyr.com/plugins/single-sign-on-for-tng/badge.svg" alt="Single Sign On For TNG vulnerability status"></a>

← Check another plugin · Free hacked-site scan