Skip to content
Laskyr

Plugins · noindex-by-path · data as of 2026-11-04

Is Noindex by Path safe? Known vulnerabilities and latest version

The latest version (1.0) has 1 known unpatched vulnerability

As of 2026-11-04, the sources we check list the newest release of Noindex by Path as affected and name no fixed version yet.

Last updated on wordpress.org on 2017-05-31, more than two years ago. Plugins that stop getting updates also stop getting security fixes.

Latest version
1.0
Last updated
2017-05-31
Active installs
60+
Known issues on record
1
Unpatched in latest
1
Tested up to WP
4.7.39

Ask search engines not to index individual pages by a relative path - which means you can set every url no matter it is a page, category listing or an … — by Marcin Kijak

What to do

  1. There is no fixed version yet. If you can live without Noindex by Path for now, deactivate it and delete it until the developer ships a fix.
  2. If you must keep it, limit who can log in (remove unused accounts, especially low-level ones) and put a web application firewall in front of the site.
  3. Watch for an update: get an email when this page changes.
  4. If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.

With WP-CLI: wp plugin get noindex-by-path --field=version shows what you run; wp plugin update noindex-by-path 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.

high 7.1 affects latest 1.0 CVE-2025-49353 · published 2025-12-31

Cross-site request forgery (CSRF) in Noindex by Path (1.0 and older)

Affected
1.0 and older
Fixed in
no fix listed yet
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 Marcin Kijak Noindex by Path noindex-by-path allows Stored XSS.This issue affects Noindex by Path: from n/a through <= 1.0.

NVD CVE-2025-49353Patchstack advisory

Recent activity

Browse vulnerabilities

Where this data comes from

Badge for your site or docs (states facts with a date, not a verdict):
Noindex by Path vulnerability status badge
<a href="https://laskyr.com/plugins/noindex-by-path"><img src="https://laskyr.com/plugins/noindex-by-path/badge.svg" alt="Noindex by Path vulnerability status"></a>

← Check another plugin · Free hacked-site scan

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit