Skip to content
Laskyr

Plugins · jquery-hover-footnotes · data as of 2026-11-04

Is jQuery Hover Footnotes safe? Known vulnerabilities and latest version

jQuery Hover Footnotes is closed on wordpress.org

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

Status
Closed 2026-06-02
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 jquery-hover-footnotes && wp plugin delete jquery-hover-footnotes

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.3 CVE-2026-10553 · published 2026-06-09

Cross-site request forgery (CSRF) in jQuery Hover Footnotes (1.4 and older)

Affected
1.4 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 Wordfence
Details from the advisory

The jQuery Hover Footnotes plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.4. This is due to missing or incorrect nonce validation on the jqFootnotes_options_subpanel function. This makes it possible for unauthenticated attackers to update the plugin's settings with arbitrary values that, because option values such as jqfoot_anchor_open, jqfoot_anchor_close, and jqfoot_title are echoed unescaped into frontend page content, can be chained into persistent Cross-Site Scripting affecting all site visitors via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. Successful exploitation of the CSRF vulnerability can be chained into stored Cross-Site Scripting, as the overwritten option values are persisted via update_option() without sanitization and rendered unescaped on the frontend.

NVD CVE-2026-10553Wordfence advisoryPlugin source

medium 6.4 CVE-2026-10738 · published 2026-06-09

Stored cross-site scripting (XSS) in jQuery Hover Footnotes (1.4 and older)

Affected
1.4 and older
Fixed in
unknown
Access needed (per CVSS)
Needs a low-level account (e.g. subscriber)
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

The jQuery Hover Footnotes plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Footnote Qualifier ('{{...}}' Syntax) in all versions up to, and including, 1.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The attribute-breakout payload (e.g., a double-quote followed by an event handler) contains no angle brackets and therefore bypasses WordPress core's wp_kses_post() filtering, which only strips disallowed HTML tags rather than sanitizing attribute contexts.

NVD CVE-2026-10738Wordfence advisoryPlugin source

Recent activity

Browse vulnerabilities

Where this data comes from

Badge for your site or docs (states facts with a date, not a verdict):
jQuery Hover Footnotes vulnerability status badge
<a href="https://laskyr.com/plugins/jquery-hover-footnotes"><img src="https://laskyr.com/plugins/jquery-hover-footnotes/badge.svg" alt="jQuery Hover Footnotes 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