Skip to content
Laskyr

Plugins · internal-link-builder · data as of 2026-11-04

Is Internal Link Builder safe? Known vulnerabilities and latest version

Internal Link Builder is closed on wordpress.org

Closed on 2026-01-08 (reason given: Security Issue). Closed plugins get no updates through WordPress, so new security holes will not be fixed for you.

Status
Closed 2026-01-08
Known issues on record
2
Unpatched in latest
0

What to do

  1. Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
  2. Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
  3. 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, once you have a replacement: wp plugin deactivate internal-link-builder && wp plugin delete internal-link-builder

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. 2 record(s) do not state which versions are affected.

medium 4.4 CVE-2025-14725 · published 2026-01-14

Stored cross-site scripting (XSS) in Internal Link Builder (1.0 and older)

Affected
1.0 and older
Fixed in
unknown
Access needed (per CVSS)
Needs an admin-level account
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

The Internal Link Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 1.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.

NVD CVE-2025-14725Wordfence advisoryPlugin source

high 7.1 CVE-2025-23989 · published 2025-01-31

Cross-site request forgery (CSRF) in Internal Link Builder (1.0 and older)

Affected
1.0 and older
Fixed in
unknown
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 Alessandro Piconi Internal Link Builder internal-link-builder allows Cross Site Request Forgery.This issue affects Internal Link Builder: from n/a through <= 1.0.

NVD CVE-2025-23989Patchstack advisory

Recent activity

Browse vulnerabilities

Where this data comes from

Badge for your site or docs (states facts with a date, not a verdict):
Internal Link Builder vulnerability status badge
<a href="https://laskyr.com/plugins/internal-link-builder"><img src="https://laskyr.com/plugins/internal-link-builder/badge.svg" alt="Internal Link Builder 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