[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fTzDzgNVXD1zzSPPWHIhx-0ziPdYQRpQMk8Z3mPTP--Q":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":19,"homepage":22,"download_link":23,"security_score":24,"vuln_count":14,"unpatched_count":14,"last_vuln_date":25,"fetched_at":26,"vulnerabilities":27,"developer":42,"crawl_stats":33,"alternatives":50,"analysis":152,"fingerprints":219},"footnotes-for-wordpress","Footnotes for WordPress","2016.1230","C. Johnson","https:\u002F\u002Fprofiles.wordpress.org\u002Fradgeek\u002F","\u003Cp>Footnotes for WordPress is a simple plugin designed with a simple aim in mind: to make\u003Cbr \u002F>\nit dead-easy to include decently-formatted footnotes in posts and pages on your\u003Cbr \u002F>\nWordPress blog.\u003C\u002Fp>\n\u003Cp>The syntax is roughly based on the common MediaWiki syntax for footnotes, but uses the\u003Cbr \u002F>\nWordPress shortcode conventions. So, to include a footnote with the text “Text,” you use:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>This is footnoted.[ref]Text[\u002Fref]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>And that’s all you need to do. When you add a footnote, Footnotes for WordPress will\u003Cbr \u002F>\ncreate a note marker at the point that the foonote appears in the text, and includes\u003Cbr \u002F>\nthe text of the footnote in a styled list of notes down the page. When a reader clicks\u003Cbr \u002F>\non the link in a JavaScript-enabled browser, a script included with the plugin will\u003Cbr \u002F>\ncreate a small bubble inline in the text, which pops up over the footnote marker for\u003Cbr \u002F>\neasy reading without losing their place. In non-JavaScript-enabled contexts, clicking\u003Cbr \u002F>\non the footnote marker jumps down the page to the text of the note.\u003C\u002Fp>\n\u003Cp>The jump is based on an unique anchor which the plugin can automatically generate for\u003Cbr \u002F>\nyou. However, if you want to create a specific ID of your own for the footnote, you\u003Cbr \u002F>\ncan do so using the \u003Ccode>name=\"...\"\u003C\u002Fcode> attribute:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>This is footnoted.[ref name=\"my-unique-id-1\"]Text[\u002Fref]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>If you define an ID for a footnote, you can also refer back to the same footnote\u003Cbr \u002F>\nlater on in the document, using the \u003Ccode>[backref name=\"...\"]\u003C\u002Fcode> shortcode.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>This is footnoted.[ref name=\"source1\"]Source 1[\u002Fref]\n\nSo is this.[ref name=\"source2\"]Source[\u002Fref]\n\nAnd this one comes from the same source as the first.[backref name=\"source1\"]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Footnotes are numbered, beginning at 1. However, you can change the numbering if you\u003Cbr \u002F>\nso desire using the \u003Ccode>number=\"...\"\u003C\u002Fcode> attribute. For example, I often use this when\u003Cbr \u002F>\nquoting from a book that contains footnotes or endnotes, in order to represent the\u003Cbr \u002F>\nnotes used by the original text.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>This is footnoted, but footnotes begin at number 42.[ref number=\"42\"]...[\u002Fref]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>You can change the text that is displayed in the note’s superscripted link from the\u003Cbr \u002F>\nnote’s number to any text or symbol that you choose using the \u003Ccode>superscript=\"...\"\u003C\u002Fcode>\u003Cbr \u002F>\nattribute. For example, to use an asterisk instead of the note number:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>This is footnoted with a good old asterisk.[ref superscript=\"*\"]...[\u002Fref]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>By default, the list of footnotes appears at the bottom of the post. However, if you\u003Cbr \u002F>\nwish them to appear somewhere above the bottom of the post, for formatting or other\u003Cbr \u002F>\nreasons, you can do so using the \u003Ccode>[references\u002F]\u003C\u002Fcode> shortcode:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>This is footnoted.[ref]Text[\u002Fref]\n\nAs are some[ref]Text[\u002Fref] other things.\n\n[references\u002F]\n\nSee also: Endnotes.\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Which will cause the two footnotes to appear beneath the second paragraph but above\u003Cbr \u002F>\nthe “See also:” text.\u003C\u002Fp>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\n\u003Cp>To create a footnote, use \u003Ccode>[ref]...[\u002Fref]\u003C\u002Fcode> to wrap the text of your note.\u003C\u002Fp>\n\u003Cp>Example: \u003Ccode>This is footnoted.[ref]This is the text of the of the footnote.[\u002Fref]\u003C\u002Fcode>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Normally footnotes use numbered superscripts to indicate the footnote, beginning\u003Cbr \u002F>\nwith 1. You can choose to use symbols instead, like *, **, †, etc. To use custom\u003Cbr \u002F>\ntext for a footnote’s superscript, use \u003Ccode>[ref superscript=\"*\"]...[\u002Fref]\u003C\u002Fcode>, and\u003Cbr \u002F>\nreplace the asterisk with whatever symbol or text you want to use.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Normally footnotes begin at 1 and count up towards infinity. If you want to use\u003Cbr \u002F>\nnumbered subscripts but need to reset the number they count from, use the \u003Ccode>number\u003C\u002Fcode>\u003Cbr \u002F>\nattribute. For example, if you want the current subscript to be numbered 128, and\u003Cbr \u002F>\nfor subsequent subscripts to be numbered 129, 130, etc., use:\u003Cbr \u002F>\n    [ref number=”128″]…[\u002Fref].\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>To create a footnote with a specific unique ID, instead of the one that the plugin\u003Cbr \u002F>\nwill automatically generate for you, use \u003Ccode>[ref name=\"...\"]...[\u002Fref]\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cp>Example: \u003Ccode>This is footnoted.[ref name=\"my-unique-id\"]This is the note text.[\u002Fref]\u003C\u002Fcode>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>If you define an ID for a footnote, you can also refer back to the same\u003Cbr \u002F>\nfootnote later on in the document, using the \u003Ccode>[backref name=\"...\"]\u003C\u002Fcode>\u003Cbr \u002F>\nshortcode.\u003C\u002Fp>\n\u003Cp>This is footnoted.[ref name=”source1″]Source 1[\u002Fref]\u003C\u002Fp>\n\u003Cp>So is this.[ref name=”source2″]Source[\u002Fref]\u003C\u002Fp>\n\u003Cp>And this one comes from the same source as the first.[backref name=”source1″]\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>To force the plugin to display notes at a different location instead of at the bottom\u003Cbr \u002F>\nof the post, use \u003Ccode>[references\u002F]\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cp>Example:\u003C\u002Fp>\n\u003Cp>This is footnoted.[ref]Text[\u002Fref]\u003C\u002Fp>\n\u003Cp>As are some[ref]Text[\u002Fref] other things.\u003C\u002Fp>\n\u003Cp>[references\u002F]\u003C\u002Fp>\n\u003Cp>See also: Endnotes.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>If you wish to change how footnotes are styled, you can alter them in your\u003Cbr \u002F>\nWordPress theme stylesheet, or using JavaScript. The default elements and\u003Cbr \u002F>\nclasses are \u003Ccode>\u003Ca class=\"footnoted\">\u003C\u002Fcode> for superscript links to footnotes,\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003C\u003C\u002Fp>\n\u003Cp>ol class=”footnotes”> for the list of references, and\u003C\u002Fp>\n\u003Cli> for each individual footnote. So, for example, to\u003Cbr \u002F>\n    display footnotes at the bottom in a simple list, rather than in individual\u003Cbr \u002F>\n    boxes with “Note” headers, add the following line to your Theme stylesheet:\u003C\u002Fli>\n\u003C\u002Fp>\n\u003Cpre>\u003Ccode>    ol.footnotes li {\n        background: transparent !important;\n        padding: 0px !important;\n        border: none !important;\n        margin: 0.5em 2em !important;\n    }\n\nThe use of `!important` will ensure that it overrides the default styles\nset up by the plugin.\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cul>\n\u003Cli>\n\u003Cp>Alternatively, if you want to change the CSS class which is applied to to\u003Cbr \u002F>\nthe footnotes list, you can do so using the \u003Ccode>class\u003C\u002Fcode> parameter on\u003Cbr \u002F>\n    [references\u002F]:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>This is a test.[ref]Lewis (2000).[\u002Fref]\n\n\u003Ch3>Notes\u003C\u002Fh3>\n\n[references class=\"compact\" \u002F]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>… which will produce the following HTML:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003Cp>This is a test.\u003Csup>[\u003Ca href=\"#test-n-1\" class=\"footnoted\"\nid=\"to-test-n-1\">1\u003C\u002Fa>]\u003C\u002Fsup>\u003C\u002Fp>\n\n\u003Ch3>Notes\u003C\u002Fh3>\n\u003Col class=\"compact\">\n\u003Cli class=\"footnote\" id=\"test-n-1\">\u003Cstrong>\u003Csup>[1]\u003C\u002Fsup>\u003C\u002Fstrong> Lewis\n(2000). \u003Ca class=\"note-return\" href=\"#to-test-n-1\">↩\u003C\u002Fa>\u003C\u002Fli\n>\u003C\u002Fol>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Since the default styling is based on children of \u003Ccode>ol.footnotes\u003C\u002Fcode>, those\u003Cbr \u002F>\nstyles will not apply, and you can apply whatever styles you wish to the\u003Cbr \u002F>\nclass that you’ve created.\u003C\u002Fp>\n\u003Ch3>Changes from version 2010.0309 to version 2010.0822\u003C\u002Fh3>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Added \u003Ccode>[backref name=\"...\" \u002F]\u003C\u002Fcode> shortcode allowing you to refer back to a note with an established name\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Eliminated a bug which caused duplicate IDs if you tried to set up multiple sections of footnotes in the same post using repeated \u003Ccode>[references\u002F]\u003C\u002Fcode> codes.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Added \u003Ccode>[references class=\"foo\" \u002F]\u003C\u002Fcode> syntax, allowing user to supply their own class for CSS re-styling purposes.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Tested for and verified compatibility up to WordPress 3.0.1 and WordPress trunk.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Changes from version 2010.0306 to version 2010.0309\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Eliminates a harmless but potentially annoying source of “Missing argument” warnings from PHP\u003C\u002Fli>\n\u003C\u002Ful>\n","Footnotes for WordPress enables easy-to-use fancy footnotes for WordPress posts.",100,10403,80,1,"2016-12-30T16:46:00.000Z","4.7.32","2.9","",[20,21],"footnotes","formatting","http:\u002F\u002Fprojects.radgeek.com\u002Fwp-footnotes.php","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffootnotes-for-wordpress.2016.1230.zip",64,"2025-04-01 00:00:00","2026-03-15T15:16:48.613Z",[28],{"id":29,"url_slug":30,"title":31,"description":32,"plugin_slug":4,"theme_slug":33,"affected_versions":34,"patched_in_version":33,"severity":35,"cvss_score":36,"cvss_vector":37,"vuln_type":38,"published_date":25,"updated_date":39,"references":40,"days_to_patch":33},"CVE-2025-31735","footnotes-for-wordpress-authenticated-contributor-stored-cross-site-scripting","Footnotes for WordPress \u003C= 2016.1230 - Authenticated (Contributor+) Stored Cross-Site Scripting","The Footnotes for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 2016.1230 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.",null,"\u003C=2016.1230","medium",6.4,"CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:L\u002FUI:N\u002FS:C\u002FC:L\u002FI:L\u002FA:N","Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')","2025-04-09 13:25:59",[41],"https:\u002F\u002Fwww.wordfence.com\u002Fthreat-intel\u002Fvulnerabilities\u002Fid\u002Fecebc618-2d39-4284-bb31-59de0e17bc63?source=api-prod",{"slug":43,"display_name":7,"profile_url":8,"plugin_count":44,"total_installs":45,"avg_security_score":46,"avg_patch_time_days":47,"trust_score":48,"computed_at":49},"radgeek",2,10100,81,2085,66,"2026-04-04T11:03:53.640Z",[51,75,93,106,129],{"slug":52,"name":53,"version":54,"author":55,"author_profile":56,"description":57,"short_description":58,"active_installs":59,"downloaded":60,"rating":61,"num_ratings":62,"last_updated":63,"tested_up_to":64,"requires_at_least":65,"requires_php":66,"tags":67,"homepage":70,"download_link":71,"security_score":72,"vuln_count":14,"unpatched_count":73,"last_vuln_date":74,"fetched_at":26},"footnotes-made-easy","Footnotes Made Easy","3.1.0","Patrick Lumumba","https:\u002F\u002Fprofiles.wordpress.org\u002Flumiblog\u002F","\u003Cp>Footnotes Made Easy is a simple, but powerful, method of adding footnotes to your posts and pages.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Key features include…\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Simple footnote insertion via double parentheses\u003C\u002Fli>\n\u003Cli>Combine identical notes\u003C\u002Fli>\n\u003Cli>Solution for paginated posts\u003C\u002Fli>\n\u003Cli>Suppress Footnotes on specific page types\u003C\u002Fli>\n\u003Cli>Option to display ‘pretty’ tooltips using jQuery\u003C\u002Fli>\n\u003Cli>Lots of configuration options\u003C\u002Fli>\n\u003Cli>And much, much more!\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Footnotes Made Easy is a fork of \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdrzax\u002Fwp-footnotes\" title=\"Github - wp-footnotes\" rel=\"nofollow ugc\">WP Footnotes\u003C\u002Fa>, a plugin by Simon Elvery which was abandoned some years ago\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Please visit the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Flumumbapl\u002Ffootnotes-made-easy\u002F\" title=\"Github\" rel=\"nofollow ugc\">Github page\u003C\u002Fa> for the latest code development, planned enhancements and known issues\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Ch3>Getting Started\u003C\u002Fh3>\n\u003Cspan class=\"embed-youtube\" style=\"text-align:center; display: block;\">\u003Ciframe loading=\"lazy\" class=\"youtube-player\" width=\"750\" height=\"422\" src=\"https:\u002F\u002Fwww.youtube.com\u002Fembed\u002FLuXMb8Hz4tc?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent\" allowfullscreen=\"true\" style=\"border:0;\" sandbox=\"allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox\">\u003C\u002Fiframe>\u003C\u002Fspan>\n\u003Cp>Creating a footnote is incredibly simple – you just need to include your footnote in double parentheses, such as this…\u003C\u002Fp>\n\u003Cp>This is a sentence ((and this is your footnote)).\u003C\u002Fp>\n\u003Cp>The footnote will then appear at the bottom of your post\u002Fpage.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Important note:\u003C\u002Fstrong> Make sure you include a space before your opening double parentheses or the footnote won’t work!\u003C\u002Fp>\n\u003Ch3>Options\u003C\u002Fh3>\n\u003Cp>You have a fair few options on how the identifier links, footnotes and back-links look which can be found in the WordPress admin area under ‘Settings -> Footnotes’.\u003C\u002Fp>\n\u003Ch3>Paginated Posts\u003C\u002Fh3>\n\u003Cp>Some of you seem to like the paginating post, which is kind of problematic. By default, each page of your post will have its own set of footnotes at the bottom and the numbering will start again from 1 for each page.\u003C\u002Fp>\n\u003Cp>The only way to get around this is to know how many posts are on each page and tell Footnotes Made Easy what number you want the list to start at for each of the pages. So at some point on each page (that is, between each \u003Ccode>\u003C!--nextpage-->\u003C\u002Fcode> tag) you need to add a tag to let the plugin know what number the footnotes on this page should start at. The tag should look like this \u003Ccode>\u003C!--startnum=5-->\u003C\u002Fcode> where “5” is the number you want the footnotes for this page to start at.\u003C\u002Fp>\n\u003Ch3>Referencing\u003C\u002Fh3>\n\u003Cp>Sometimes it’s useful to be able to refer to a previous footnote a second (or third, or fourth…) time. To do this, you can either simply insert the exact same text as you did the first time and the identifier should simply reference the previous note. Alternatively, if you don’t want to do all that typing again, you can construct a footnote like this: \u003Ccode>((ref:1))\u003C\u002Fcode> and the identifier will reference the footnote with the given number.\u003C\u002Fp>\n\u003Cp>Even though it’s a little more typing, using the exact text method is much more robust. The number referencing will not work across multiple pages in a paged post (but will work within the page). Also, if you use the number referencing system you risk them identifying the incorrect footnote if you go back and insert a new footnote and forget to change the referenced number.\u003C\u002Fp>\n\u003Ch3>Available in 8 Languages\u003C\u002Fh3>\n\u003Cp>Footnotes Made Easy is fully internationalized, and ready for translations.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Many thanks to the following translators for their contributions:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fdartiss\u002F\" rel=\"nofollow ugc\">David Artiss\u003C\u002Fa>, English (UK)\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fmarkscottrobson\u002F\" rel=\"nofollow ugc\">Mark Robson\u003C\u002Fa>, English (UK)\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fyayannabelle\u002F\" rel=\"nofollow ugc\">Annabelle W\u003C\u002Fa>, English (UK)\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fmaboroshin\u002F\" rel=\"nofollow ugc\">maboroshin\u003C\u002Fa>, Japanese\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fwplmillet\u002F\" rel=\"nofollow ugc\">Laurent MILLET\u003C\u002Fa>, French (France)\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fcansmile\u002F\" rel=\"nofollow ugc\">B. Cansmile Cha\u003C\u002Fa>, Korean \u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fdanbilabs\u002F\" rel=\"nofollow ugc\">danbilabs\u003C\u002Fa>, Korean\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fdanbilabs\u002F\" rel=\"nofollow ugc\">denelan\u003C\u002Fa>, Dutch \u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fpsmits1567\u002F\" rel=\"nofollow ugc\">Peter Smits\u003C\u002Fa>, Dutch\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fnekojonez\u002F\" rel=\"nofollow ugc\">Pieterjan Deneys\u003C\u002Fa>, Dutch (Belgium)\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Falexvgrey\u002F\" rel=\"nofollow ugc\">Alex Grey\u003C\u002Fa>, Russian\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>If you would like to add a translation to this plugin then please head to our \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Ffootnotes-made-easy\" title=\"Translating WordPress\" rel=\"nofollow ugc\">Translating WordPress\u003C\u002Fa> page\u003C\u002Fstrong>\u003C\u002Fp>\n","Allows post authors to easily add and manage footnotes in posts.",2000,55299,92,38,"2025-11-29T18:04:00.000Z","6.9.4","4.6","7.4",[68,20,21,69],"bibliography","reference","https:\u002F\u002Flumumbas.blog\u002Fplugins\u002Ffootnotes-made-easy\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffootnotes-made-easy.3.1.0.zip",97,0,"2025-11-03 16:03:22",{"slug":76,"name":77,"version":78,"author":79,"author_profile":80,"description":81,"short_description":82,"active_installs":83,"downloaded":84,"rating":11,"num_ratings":85,"last_updated":86,"tested_up_to":64,"requires_at_least":87,"requires_php":18,"tags":88,"homepage":91,"download_link":92,"security_score":11,"vuln_count":73,"unpatched_count":73,"last_vuln_date":33,"fetched_at":26},"blank-footnotes","Blank Footnotes","1.6.6","Corrado Franco","https:\u002F\u002Fprofiles.wordpress.org\u002Fconraid\u002F","\u003Cp>This plugin allows one to create footnotes by using markdown notation.\u003Cbr \u002F>\nIt is for footnotes only. No other markdown tag is taken into account\u003C\u002Fp>\n\u003Cp>Example:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>I have more [^1] to say up here.\n\n[^1]: To say down here.\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>If used with jetpack and enabled markdown, it only shows the buttons without modifying the text content.\u003Cbr \u002F>\nUnlike jetpack-markdown, footnotes will appear in the exact point where they have been inserted. To go back to text mode click on the footnote number.\u003C\u002Fp>\n\u003Cp>N.B\u003Cbr \u002F>\nThis plugin also works with Gutenberg. But the button only appears in the Classic Editor.\u003Cbr \u002F>\nFor now with Gutenberg enter the codes directly.\u003C\u002Fp>\n\u003Ch3>Configuration\u003C\u002Fh3>\n\u003Cp>No configuration is necessary.\u003C\u002Fp>\n\u003Cp>Considering that this plugin, like others working with “markdown”, parsing the page every time I load it, I highly recommend using a caching plugin.\u003C\u002Fp>\n","Simple plugin to show footnotes using markdown notation.",300,7495,5,"2025-11-28T17:45:00.000Z","4.4",[89,20,21,90,69],"footnote","notes","https:\u002F\u002Fgithub.com\u002Fconraid\u002Fblank-footnotes","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fblank-footnotes.1.6.6.zip",{"slug":94,"name":95,"version":96,"author":97,"author_profile":98,"description":99,"short_description":58,"active_installs":11,"downloaded":100,"rating":11,"num_ratings":101,"last_updated":102,"tested_up_to":64,"requires_at_least":103,"requires_php":66,"tags":104,"homepage":18,"download_link":105,"security_score":11,"vuln_count":73,"unpatched_count":73,"last_vuln_date":33,"fetched_at":26},"awesome-footnotes","Footnotes & Content","3.9.3","Golemiq","https:\u002F\u002Fprofiles.wordpress.org\u002Fawesomefootnotes\u002F","\u003Cp>\u003Cstrong>Footnotes & Content\u003C\u002Fstrong> plugin is a powerful method of adding \u003Cstrong>footnotes\u003C\u002Fstrong> into your posts and pages. You can have as many \u003Cstrong>footnotes\u003C\u002Fstrong> as you like pretty easily in every page, post or ACF block, WooCommerce is also supported. That is the fastest footnote plugin which is using extremely low resources – you wont even notice that it is there.\u003C\u002Fp>\n\u003Cp>You can visit the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fsdobreff\u002Fawesome-footnotes\u002F\" title=\"Github\" rel=\"nofollow ugc\">Github page\u003C\u002Fa> for the latest code development, or if you want to report an issue with the code.\u003C\u002Fp>\n\u003Cp>To gain more control over WP, directly from the WP admin – try out our plugin \u003Cstrong>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002F0-day-analytics\u002F\" rel=\"ugc\">0 day analytics\u003C\u002Fa>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch3>Key features include…\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Simple footnote insertion via markup of choice (default – double parentheses)\u003C\u002Fli>\n\u003Cli>Gutenberg support\u003C\u002Fli>\n\u003Cli>Combine identical \u003Cstrong>footnotes\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Paginated posts are supported\u003C\u002Fli>\n\u003Cli>Suppress \u003Cstrong>Footnotes\u003C\u002Fstrong> on specific page types\u003C\u002Fli>\n\u003Cli>Option to display ‘pretty’ tooltips using jQuery\u003C\u002Fli>\n\u003Cli>Option to display footnotes as tooltips using vanilla JS\u003C\u002Fli>\n\u003Cli>Lots of configuration options\u003C\u002Fli>\n\u003Cli>Different footnotes settings per post – you can use different settings on Post level – changing styles and UI\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Footnotes & Content\u003C\u002Fstrong> plugin is designed to ease the creation of a new footnote. It also gives you the ability to easily switch from most of the existing \u003Cstrong>footnotes\u003C\u002Fstrong> plugins to this one. Lets face it – almost 100% of them are abandoned or in awful condition. It supports PHP8, it is written using best practices and follows the WordPress standards, give it a try. You can quickly check the plugin \u003Ca href=\"https:\u002F\u002Fplayground.wordpress.net\u002F?plugin=awesome-footnotes&networking=yes\" title=\"WP Playground\" rel=\"nofollow ugc\">here\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>Technical specification…\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Designed for both single and multi-site installations\u003C\u002Fli>\n\u003Cli>PHP8 fully compatible\u003C\u002Fli>\n\u003Cli>PHP multibyte must be installed\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Getting Started\u003C\u002Fh3>\n\u003Cp>Creating a footnote is incredibly simple – you just need to include your \u003Cstrong>footnote\u003C\u002Fstrong> in double parentheses (default, but you can change that), such as this:\u003C\u002Fp>\n\u003Cp>This is a sentence \u003Cstrong>((and this is your footnote))\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>You can change the markup for the footnote in the settings page of the plugin.\u003C\u002Fp>\n\u003Cp>The footnote will then appear at the bottom of your post\u002Fpage.\u003C\u002Fp>\n\u003Cp>Don’t put footnotes in short description \u002F excerpts – the plugin won’t work there by design.\u003C\u002Fp>\n\u003Cp>Or you can use a shortcode for where you want your footnotes to appear. The shortcode is “\u003Ccode>awef_show_footnotes\u003C\u002Fcode>“. The shortcode also accepts a parameter of the post id in format of ‘post_id=1’. If not presented, the global \\WP_Post object will be used.\u003C\u002Fp>\n\u003Cp>You can also use a PHP call in your templates or whatever you like by using the following:\u003Cbr \u002F>\n    AWEF\\Controllers\\Footnotes_Formatter::show_footnotes( array( ‘post_id’ => 1 ) );\u003Cbr \u002F>\nNote: If you choose this way (above), you have to go to the plugin settings, and set “Do not autodisplay in posts” to true.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Advanced Custom Fields (ACF)\u003C\u002Fstrong> are also supported out of the box – just read and keep in mind this:\u003C\u002Fp>\n\u003Cp>Unfortunately there are limitations with the \u003Cstrong>ACF\u003C\u002Fstrong> because of its block structure. There is no way to guess how many blocks are there, which is first, second, are there more blocks or not … So every block will show its own footnotes, and shortcodes are not working outside them. Currently there is no way to achieve that functionality. So they are treated more like endnotes if there are multiple blocks using the footnotes tags.\u003C\u002Fp>\n\u003Cp>What plugin does is to keep track of the footnotes and keep proper numbering among the blocks (again there is no way to guess which is which, so they are parsed in order of their callings from backend, but they can be shown in entirely different places on the front end.)\u003C\u002Fp>\n\u003Cp>\u003Cstrong>WooCommerce\u003C\u002Fstrong> (including new product editor) is also supported.\u003C\u002Fp>\n\u003Cp>Unlike any other plugin, this one gives you the ability to have different settings for different posts. When editing post, you can change the setting for the plugin which will apply for that specific post, and others will keep using the global settings. If you think that this is too much, you can always disable this from advanced settings.\u003C\u002Fp>\n\u003Ch3>Other plugins compatibility\u003C\u002Fh3>\n\u003Cp>There are plugins with which that one is 100% compatible – meaning that you can directly jump from them to this one:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdrzax\u002Fwp-footnotes\" title=\"Github - wp-footnotes\" rel=\"nofollow ugc\">WP Footnotes\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Ffootnotes-made-easy\" title=\"WordPress.org - footnotes-made-easy\" rel=\"ugc\">Footnotes Made Easy\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Options\u003C\u002Fh3>\n\u003Cp>You have a fair few options on how the identifier links, footnotes and back-links look which can be found in the WordPress admin area either on the stand alone page, or under Settings -> Footnotes – that depends on your desired setting in the plugin.\u003C\u002Fp>\n\u003Ch3>Shortcode options\u003C\u002Fh3>\n\u003Cpre>\u003Ccode>[awef_show_footnotes] Is the shortcode you should use. Inside the post content, there is nothing more that you have to do.\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>If you want to use the shortcode outside of the post content, then you need to add the post id as a parameter:\u003Cbr \u002F>\n    [awef_show_footnotes post_id=1]\u003Cbr \u002F>\nIf outside of the post content, and there is no parameter of the post id provided, then the plugin will try to use the global post if presented.\u003C\u002Fp>\n\u003Ch3>Paginated Posts\u003C\u002Fh3>\n\u003Cp>Some of you seem to like paginating post, which is kind of problematic. By default each page of your post will have it’s own set of footnotes at the bottom and the numbering will start again from 1 for each page.\u003C\u002Fp>\n\u003Cp>The only way to get around this is to know how many posts are on each page and tell Awesome Footnotes what number you want the list to start at for each of the pages. So at some point on each page (that is, between each \u003Ccode>\u003C!--nextpage-->\u003C\u002Fcode> tag) you need to add a tag to let the plugin know what number the footnotes on this page should start at. The tag should look like this \u003Ccode>\u003C!--startnum=5-->\u003C\u002Fcode> where “5” is the number you want the footnotes for this page to start at.\u003C\u002Fp>\n\u003Ch3>Referencing\u003C\u002Fh3>\n\u003Cp>Sometimes it’s useful to be able to refer to a previous footnote a second (or third, or fourth…) time. To do this, you can either simply insert the exact same text as you did the first time and the identifier should simply reference the previous note. Alternatively, if you don’t want to do all that typing again, you can construct a footnote like this: \u003Ccode>((ref:1))\u003C\u002Fcode> and the identifier will reference the footnote with the given number.\u003C\u002Fp>\n\u003Cp>Even though it’s a little more typing, using the exact text method is much more robust. The number referencing will not work across multiple pages in a paged post (but will work within the page). Also, if you use the number referencing system you risk them identifying the incorrect footnote if you go back and insert a new footnote and forget to change the referenced number.\u003C\u002Fp>\n\u003Ch3>FAQ Schema Usage Guide\u003C\u002Fh3>\n\u003Ch3>For Administrators\u003C\u002Fh3>\n\u003Col>\n\u003Cli>\u003Cstrong>Edit any post or page\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Scroll to the “Awesome Footnotes – Settings” meta box\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Click the “FAQ Schema” tab\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Click “Add FAQ Item”\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Fill in the Question and Answer fields\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Repeat for additional FAQs\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Use move up\u002Fdown buttons to reorder\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Click Remove to delete items\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Save\u002FUpdate the post\u003C\u002Fstrong>\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>For Content Display\u003C\u002Fh3>\n\u003Col>\n\u003Cli>\u003Cstrong>In the post content editor, add:\u003C\u002Fstrong>\u003Cbr \u002F>\n   \u003Ccode>[awef_faq]\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Publish\u002FUpdate the post\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>View the post on the frontend\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>FAQs will display at the shortcode location\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>JSON-LD schema automatically added to \u003Ccode>\u003Chead>\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>For Developers\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Get FAQ data programmatically:\u003C\u002Fstrong>\u003Cbr \u002F>\n    `php\u003Cbr \u002F>\nuse AWEF\\Controllers\\Post_Settings;\u003C\u002Fp>\n\u003Cp>$post_id = get_the_ID();\u003Cbr \u002F>\n$faqs = Post_Settings::get_faq_schema( $post_id );\u003C\u002Fp>\n\u003Cp>foreach ( $faqs as $faq ) {\u003Cbr \u002F>\n    echo $faq[‘question’];\u003Cbr \u002F>\n    echo $faq[‘answer’];\u003Cbr \u002F>\n}\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Check if FAQ shortcode is used:\u003C\u002Fstrong>\u003Cbr \u002F>\n    \u003Ccode>php\u003Cbr \u002F>\n$content = get_post_field( 'post_content', $post_id );\u003Cbr \u002F>\nif ( has_shortcode( $content, 'awef_faq' ) ) {\u003Cbr \u002F>\n    \u002F\u002F FAQ shortcode is present\u003Cbr \u002F>\n}\u003C\u002Fcode>\u003C\u002Fp>\n",4136,4,"2026-01-05T20:40:00.000Z","6.0",[20,21,90,69],"https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fawesome-footnotes.3.9.3.zip",{"slug":107,"name":108,"version":109,"author":110,"author_profile":111,"description":112,"short_description":113,"active_installs":114,"downloaded":115,"rating":116,"num_ratings":117,"last_updated":118,"tested_up_to":64,"requires_at_least":119,"requires_php":120,"tags":121,"homepage":126,"download_link":127,"security_score":11,"vuln_count":14,"unpatched_count":73,"last_vuln_date":128,"fetched_at":26},"tinymce-advanced","Advanced Editor Tools","5.9.2","Andrew Ozz","https:\u002F\u002Fprofiles.wordpress.org\u002Fazaozz\u002F","\u003Cp>Advanced Editor Tools (previously TinyMCE Advanced) introduces a “Classic Paragraph” block for the block editor (Gutenberg).\u003Cbr \u002F>\nIf you are not quite ready to switch to the block editor, or have plugins that cannot be used there (yet), using the Classic Paragraph block is your best option. It lets you to continue to use the familiar TinyMCE editor for most tasks, and at the same time gives you full access to all blocks and new features in the block editor.\u003C\u002Fp>\n\u003Cp>Version 5.5 continues to improve and enhance the new features introduced in version 5.0 of the plugin. It includes an improved “Clear Formatting” button, several advanced settings for tables, and importing and exporting of the settings to a file.\u003C\u002Fp>\n\u003Cp>If you want to continue to use the previous (“classic”) editor in WordPress 5.0 and newer, this plugin has an option to replace the new editor with the previous one. If you prefer to have access to both editors side by side or to allow your users to switch editors, it would be better to install the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fclassic-editor\u002F\" rel=\"ugc\">Classic Editor plugin\u003C\u002Fa>. Advanced Editor Tools is fully compatible with the classic editor plugin and similar plugins that restore use of the previous WordPress editor.\u003C\u002Fp>\n\u003Cp>As always this plugin will let you add, remove and arrange the buttons that are shown on the Visual Editor toolbar in the Classic Paragraph and Classic blocks in the block editor, and in the classic editor (when enabled by a plugin). There you can configure up to four rows of buttons including Font Sizes, Font Family, text and background colors, tables, etc.\u003C\u002Fp>\n\u003Cp>It includes 15 plugins for \u003Ca href=\"https:\u002F\u002Fwww.tiny.cloud\u002F\" rel=\"nofollow ugc\">TinyMCE\u003C\u002Fa> that are automatically enabled or disabled depending on the buttons you have chosen.\u003Cbr \u002F>\nIn addition this plugin adds options for keeping the paragraph tags in text mode and importing the CSS classes from the theme’s editor-style.css.\u003C\u002Fp>\n\u003Ch4>Some of the features added by this plugin\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>“Classic Paragraph” block that can be used instead of or together with the standard Paragraph block.\u003C\u002Fli>\n\u003Cli>An option to set the Classic Paragraph or Classic block as the default block in the block editor.\u003C\u002Fli>\n\u003Cli>Supports converting of most default blocks to classic paragraphs, and from classic paragraphs back to the default blocks.\u003C\u002Fli>\n\u003Cli>Support for creating and editing tables in the Classic blocks and the classic editor.\u003C\u002Fli>\n\u003Cli>More options when inserting lists in the Classic blocks and the classic editor.\u003C\u002Fli>\n\u003Cli>Search and Replace in the Classic blocks and the classic editor.\u003C\u002Fli>\n\u003Cli>Ability to set Font Family and Font Sizes in the Classic blocks and the classic editor.\u003C\u002Fli>\n\u003Cli>And many others.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Privacy\u003C\u002Fh4>\n\u003Cp>Advanced Editor Tools does not collect or store any user related data. It does not set cookies, and it does not connect to any third-party websites. It only uses functionality that is available in \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002F\" rel=\"ugc\">WordPress\u003C\u002Fa>, and in the \u003Ca href=\"https:\u002F\u002Ftinymce.com\u002F\" rel=\"nofollow ugc\">TinyMCE editor\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>In that terms Advanced Editor Tools does not affect your website’s user privacy in any way.\u003C\u002Fp>\n","Extends and enhances the block editor (Gutenberg) and the classic editor (TinyMCE).",2000000,35126516,90,351,"2025-12-08T15:02:00.000Z","5.9","5.6",[122,123,124,21,125],"block-editor","classic-editor","editor","gutenberg","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Ftinymce-advanced\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ftinymce-advanced.5.9.2.zip","2014-09-08 00:00:00",{"slug":130,"name":131,"version":132,"author":133,"author_profile":134,"description":135,"short_description":136,"active_installs":137,"downloaded":138,"rating":139,"num_ratings":140,"last_updated":141,"tested_up_to":142,"requires_at_least":143,"requires_php":18,"tags":144,"homepage":149,"download_link":150,"security_score":151,"vuln_count":73,"unpatched_count":73,"last_vuln_date":33,"fetched_at":26},"advanced-excerpt","Advanced Excerpt","4.4.1","WPKube","https:\u002F\u002Fprofiles.wordpress.org\u002Fwpkube\u002F","\u003Cp>This plugin adds several improvements to WordPress’ default way of creating excerpts.\u003C\u002Fp>\n\u003Col>\n\u003Cli>Keeps HTML markup in the excerpt (and you get to choose which tags are included)\u003C\u002Fli>\n\u003Cli>Trims the excerpt to a given length using either character count or word count\u003C\u002Fli>\n\u003Cli>Only the ‘real’ text is counted (HTML is ignored but kept)\u003C\u002Fli>\n\u003Cli>Customizes the excerpt length and the ellipsis character that are used\u003C\u002Fli>\n\u003Cli>Completes the last word or sentence in an excerpt (no weird cuts)\u003C\u002Fli>\n\u003Cli>Adds a \u003Cem>read-more\u003C\u002Fem> link to the text\u003C\u002Fli>\n\u003Cli>Ignores custom excerpts and use the generated one instead\u003C\u002Fli>\n\u003Cli>Theme developers can use \u003Ccode>the_advanced_excerpt()\u003C\u002Fcode> for even more control (see the FAQ)\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Most of the above features are optional and\u002For can be customized by the user or theme developer.\u003C\u002Fp>\n\u003Cp>Banner image credit – \u003Ca href=\"https:\u002F\u002Fwww.flickr.com\u002Fphotos\u002Fchillihead\u002F\" rel=\"nofollow ugc\">chillihead\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>Original plugin author – \u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fbasvd\" rel=\"nofollow ugc\">basvd\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Useful Resources\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Ffancythemes.com\u002Fwhat-is-wordpress\u002F\" rel=\"friend nofollow ugc\">What is WordPress\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Ffancythemes.com\u002Fwordpress-themes\" rel=\"friend nofollow ugc\">Fee Themes\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Ffancythemes.com\u002Fwordpress-plugins\u002F\" rel=\"friend nofollow ugc\">plugins\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n","Control the appearance of WordPress post excerpts",80000,1542295,86,101,"2024-01-19T20:32:00.000Z","6.4.8","3.2",[145,146,21,147,148],"content","excerpt","post","post-excerpt","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Fadvanced-excerpt\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fadvanced-excerpt.4.4.1.zip",85,{"attackSurface":153,"codeSignals":186,"taintFlows":204,"riskAssessment":205,"analyzedAt":218},{"hooks":154,"ajaxHandlers":170,"restRoutes":171,"shortcodes":172,"cronEvents":184,"entryPointCount":185,"unprotectedCount":73},[155,161,166],{"type":156,"name":157,"callback":157,"priority":158,"file":159,"line":160},"filter","the_content",1000,"wp-footnotes.php",49,{"type":162,"name":163,"callback":164,"file":159,"line":165},"action","init","add_scripts",51,{"type":162,"name":167,"callback":168,"file":159,"line":169},"wp_head","add_inline_styles",52,[],[],[173,177,180],{"tag":174,"callback":175,"file":159,"line":176},"ref","shortcode",44,{"tag":178,"callback":178,"file":159,"line":179},"backref",45,{"tag":181,"callback":182,"file":159,"line":183},"references","discharge",46,[],3,{"dangerousFunctions":187,"sqlUsage":188,"outputEscaping":190,"fileOperations":73,"externalRequests":73,"nonceChecks":73,"capabilityChecks":73,"bundledLibraries":203},[],{"prepared":73,"raw":73,"locations":189},[],{"escaped":44,"rawEcho":85,"locations":191},[192,195,197,199,201],{"file":159,"line":193,"context":194},83,"raw output",{"file":159,"line":196,"context":194},88,{"file":159,"line":198,"context":194},93,{"file":159,"line":200,"context":194},94,{"file":159,"line":202,"context":194},232,[],[],{"summary":206,"deductions":207},"The \"footnotes-for-wordpress\" plugin version 2016.1230 presents a mixed security posture. On the positive side, the plugin exhibits strong practices regarding database interactions, with 100% of SQL queries utilizing prepared statements and no direct file operations or external HTTP requests detected. The static analysis also shows a limited attack surface with no identified AJAX handlers or REST API routes exposed without authentication. However, significant concerns arise from the lack of comprehensive output escaping, with only 29% of outputs properly escaped, indicating a strong potential for Cross-Site Scripting (XSS) vulnerabilities. Furthermore, the absence of any nonce checks or capability checks across its entry points (shortcodes) is a critical oversight, leaving it susceptible to various attacks if input is not properly sanitized.\n\nThe vulnerability history is particularly concerning. The plugin has a known critical vulnerability history, specifically a medium severity Cross-Site Scripting (XSS) flaw, which remains unpatched according to the provided data. The fact that the last vulnerability was documented as recent (2025-04-01) and is still unaddressed suggests a lack of active maintenance and a high likelihood of existing exploitable weaknesses. While taint analysis shows no immediate critical or high severity flows, this is likely due to the static analysis being limited or the identified vulnerabilities not triggering the taint analysis rules. The combination of these factors, especially the unpatched XSS vulnerability and lack of robust input\u002Foutput sanitization on shortcodes, creates a significant risk.\n\nIn conclusion, despite some good practices in areas like SQL handling, the \"footnotes-for-wordpress\" plugin version 2016.1230 is a high-risk component. The presence of an unpatched XSS vulnerability, coupled with insufficient output escaping and a complete lack of nonce and capability checks on its entry points, makes it a prime target for attackers. Users should exercise extreme caution and prioritize updating or replacing this plugin.",[208,211,214,216],{"reason":209,"points":210},"Unpatched CVE (Medium Severity XSS)",17,{"reason":212,"points":213},"Low percentage of properly escaped output",7,{"reason":215,"points":85},"No nonce checks",{"reason":217,"points":85},"No capability checks","2026-03-16T20:50:02.280Z",{"wat":220,"direct":233},{"assetPaths":221,"generatorPatterns":228,"scriptPaths":229,"versionParams":230},[222,223,224,225,226,227],"\u002Fwp-content\u002Fplugins\u002Ffootnotes-for-wordpress\u002Ffootnote-voodoo.css","\u002Fwp-content\u002Fplugins\u002Ffootnotes-for-wordpress\u002Ffootnote-voodoo.js","\u002Fwp-content\u002Fplugins\u002Ffootnotes-for-wordpress\u002Ffootnoted.png","\u002Fwp-content\u002Fplugins\u002Ffootnotes-for-wordpress\u002Fnote.png","\u002Fwp-content\u002Fplugins\u002Ffootnotes-for-wordpress\u002Ftip.png","\u002Fwp-content\u002Fplugins\u002Ffootnotes-for-wordpress\u002Ftip-down.png",[],[223],[231,232],"footnotes-for-wordpress\u002Ffootnote-voodoo.css?ver=2016.1230","footnotes-for-wordpress\u002Ffootnote-voodoo.js?ver=2016.1230",{"cssClasses":234,"htmlComments":237,"htmlAttributes":238,"restEndpoints":240,"jsGlobals":241,"shortcodeOutput":244},[89,235,236],"note-return","footnoted",[],[239],"data-backlink-prefix",[],[242,243],"tipUpUrl","tipDownUrl",[245,246,247,248,249,250,251],"\u003Col class=\"footnotes\">","\u003Cli class=\"footnote\">","\u003Ca class=\"note-return\" href=\"#","\u003Csup>[","\u003Ca href=\"#","\u003C\u002Fa>]\u003C\u002Fsup>","\u003C\u002Fa>\u003C\u002Fli>"]