Is WP Term Order safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (2.3.1). As of 2026-11-04. 1 issue is on record for older versions; version 2.2.0 or newer fixes all of them that state a fix. Keep WP Term Order on the latest version (2.3.1) and remove it if you do not use it.

Which versions of WP Term Order are vulnerable?

Known issues on record (newest first): Cross-site request forgery (CSRF) (2.1.0 and older, fixed in 2.2.0). The full list with sources is on this page.

What is the latest version of WP Term Order?

2.3.1, according to wordpress.org (last updated 2026-10-17). It has 6,000+ active installs.

What should I do if my WP Term Order is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update wp-term-order). 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 · wp-term-order · data as of 2026-11-04

Is WP Term Order safe? Known vulnerabilities and latest version

Latest version: 2.3.1
Last updated: 2026-10-17
Active installs: 6,000+
Known issues on record: 1
Unpatched in latest: 0
Tested up to WP: 7.1.4 · PHP 7.4+

Sort taxonomy terms your way. — by John James Jacoby

What to do

Update to the latest version (2.3.1). 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 wp-term-order --field=version shows what you run; wp plugin update wp-term-order updates it.

Check your version

Known vulnerabilities

1 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.

medium 4.3 CVE-2026-24542 · published 2026-01-23

Cross-site request forgery (CSRF) in WP Term Order (2.1.0 and older)

Affected: 2.1.0 and older
Fixed in: 2.2.0
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Cross-Site Request Forgery (CSRF) vulnerability in John James Jacoby WP Term Order wp-term-order allows Cross Site Request Forgery.This issue affects WP Term Order: from n/a through <= 2.1.0.

NVD CVE-2026-24542 Patchstack advisory

Recent activity

2026-10-17 — latest release on wordpress.org (2.3.1).
2026-01-23 — Cross-site request forgery (CSRF) disclosed (CVE-2026-24542), fixed in 2.2.0.

Free. We check the CVE feeds every day and email you only when a new issue for WP Term Order (wp-term-order) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Cross-site request forgery (CSRF) (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/wp-term-order (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/wp-term-order"><img src="https://laskyr.com/plugins/wp-term-order/badge.svg" alt="WP Term Order vulnerability status"></a>

← Check another plugin · Free hacked-site scan