{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-10553 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-10553 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-10553 is a medium-severity vulnerability in weaverlancegmailcom jQuery Hover Footnotes, published on 9 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-10553 and fix it if it is affected.\n\nWhat it is: CVE-2026-10553 is a medium-severity vulnerability in weaverlancegmailcom jQuery Hover Footnotes, published on 9 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-10553 in the wild and no public exploit code.\n\nAffected product: weaverlancegmailcom jQuery Hover Footnotes. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-10553/ (Markdown: https://insights.sbomify.com/CVE-2026-10553/index.md)","id":"CVE-2026-10553","markdown":"https://insights.sbomify.com/CVE-2026-10553/index.md","name":"CVE-2026-10553","record":{"aliases":["GHSA-ccr8-xm74-43hp"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can trick admins into updating plugin settings, leading to stored XSS affecting all site visitors.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"jQuery Hover Footnotes \u003c= 1.4 - Cross-Site Request Forgery to Plugin Settings Update","id":"CVE-2026-10553","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Unauthenticated webhook request with null notification entry could crash the Microsoft Calendar plugin.","id":"CVE-2026-10556"},"packages":[],"prev":{"headline":"Blue Captcha \u003c= 2.0.1 - Cross-Site Request Forgery via 'blcap_action' Parameter","id":"CVE-2026-10552"},"products":["jQuery Hover Footnotes"],"published":"2026-06-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-09","vendors":["weaverlancegmailcom"]},"summary":"Attackers can trick admins into updating plugin settings, leading to stored XSS affecting all site visitors.","url":"https://insights.sbomify.com/CVE-2026-10553/"}