{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-25169 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-25169 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-25169 is a low-severity vulnerability in discourse-yearly-review, published on 6 Mar 2023. 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-2023-25169 and fix it if it is affected.\n\nWhat it is: CVE-2023-25169 is a low-severity vulnerability in discourse-yearly-review, published on 6 Mar 2023. 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-2023-25169 in the wild and no public exploit code.\n\nAffected product: discourse-yearly-review. 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-2023-25169/ (Markdown: https://insights.sbomify.com/CVE-2023-25169/index.md)","id":"CVE-2023-25169","markdown":"https://insights.sbomify.com/CVE-2023-25169/index.md","name":"CVE-2023-25169","record":{"aliases":["GHSA-x2r8-v85c-x3x7"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Discourse plugin","requires_auth":"none","summary":"Anonymized user data remains linked to original accounts in Yearly Review topics, allowing potential identification of users.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"discourse_yearly_review","vendor":"discourse"}],"cvss":{"score":3.1,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"discourse-yearly-review is a discourse plugin which publishes an automated Year in Review topic. In affected versions a user present in a yearly review topic that is then anonymised will still have some data linked to its original account. This issue has been patched in commit `b3ab33bbf7` which is included in the latest version of the Discourse Yearly Review plugin. Users are advised to upgrade. Users unable to upgrade may disable the `yearly_review_enabled` setting to fully mitigate the issue. Also, it's possible to edit the anonymised user's old data in the yearly review topics manually.","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":"Yearly Review Plugin leaking anonymised users data in discourse-yearly-review","id":"CVE-2023-25169","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"PrestaShop has possible CSRF token fixation","id":"CVE-2023-25170"},"packages":[],"prev":{"headline":"Symbolic Link (Symlink) Following allowing the deletion of files and directories on the host system in wings","id":"CVE-2023-25168"},"products":["discourse-yearly-review"],"published":"2023-03-06","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-25","vendors":["discourse"]},"summary":"Anonymized user data remains linked to original accounts in Yearly Review topics, allowing potential identification of users.","url":"https://insights.sbomify.com/CVE-2023-25169/"}