{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-43827 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-43827 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-43827 is a medium-severity vulnerability in discourse-footnote, published on 14 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-43827 and fix it if it is affected.\n\nWhat it is: CVE-2021-43827 is a medium-severity vulnerability in discourse-footnote, published on 14 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-43827 in the wild and no public exploit code.\n\nAffected product: discourse-footnote. 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-2021-43827/ (Markdown: https://insights.sbomify.com/CVE-2021-43827/index.md)","id":"CVE-2021-43827","markdown":"https://insights.sbomify.com/CVE-2021-43827/index.md","name":"CVE-2021-43827","record":{"aliases":["GHSA-58vr-c56v-qr57"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Discourse footnote plugin","requires_auth":"low_privilege","summary":"A null reference error in JavaScript occurs when rendering inline footnotes wrapped in anchor tags, causing errors on topic pages for Discourse users.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"discourse_footnote","vendor":"discourse"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-755","name":"Improper Handling of Exceptional Conditions"}],"description":"discourse-footnote is a library providing footnotes for posts in Discourse. ### Impact When posting an inline footnote wrapped in `\u003ca\u003e` tags (e.g. `\u003ca\u003e^[footnote]\u003c/a\u003e`, the resulting rendered HTML would include a nested `\u003ca\u003e`, which is stripped by Nokogiri because it is not valid. This then caused a javascript error on topic pages because we were looking for an `\u003ca\u003e` element inside the footnote reference span and getting its ID, and because it did not exist we got a null reference error in javascript. Users are advised to update to version 0.2. As a workaround editing offending posts from the rails console or the database console for self-hosters, or disabling the plugin in the admin panel can mitigate this issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Inline footnotes wrapped in \u003ca\u003e tags can cause errors in discourse-footnotes","id":"CVE-2021-43827","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Improper Privilege Management in Patrowl","id":"CVE-2021-43828"},"packages":[],"prev":{"headline":"Crash when tunneling TCP over HTTP in Envoy","id":"CVE-2021-43826"},"products":["discourse-footnote"],"published":"2021-12-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["discourse"]},"summary":"A null reference error in JavaScript occurs when rendering inline footnotes wrapped in anchor tags, causing errors on topic pages for Discourse users.","url":"https://insights.sbomify.com/CVE-2021-43827/"}