{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-22469 exists.","fix":"No fix has been published for CVE-2023-22469 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-22469 is a medium-severity vulnerability in nextcloud security-advisories, published on 10 Jan 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-22469 and fix it if it is affected.\n\nWhat it is: CVE-2023-22469 is a medium-severity vulnerability in nextcloud security-advisories, published on 10 Jan 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-22469 exists.\n\nAffected product: nextcloud security-advisories. 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-22469/ (Markdown: https://insights.sbomify.com/CVE-2023-22469/index.md)","id":"CVE-2023-22469","markdown":"https://insights.sbomify.com/CVE-2023-22469/index.md","name":"CVE-2023-22469","record":{"aliases":["GHSA-8fjp-w9gp-j5hq"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Nextcloud Deck plugin","requires_auth":"low_privilege","summary":"Unauthorized users can access cached preview data of Nextcloud Deck cards they lack permission to view, exposing sensitive information.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"deck","vendor":"nextcloud"}],"cvss":{"score":5.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-922","name":"Insecure Storage of Sensitive Information"}],"description":"Deck is a kanban style organization tool aimed at personal planning and project organization for teams integrated with Nextcloud. When getting the reference preview for Deck cards the user has no access to, unauthorized user could eventually get the cached data of a user that has access. There are currently no known workarounds. It is recommended that the Nextcloud app Deck is upgraded to 1.8.2.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Nextcloud Deck card vulnerable to data leak to unauthorized users via reference preview cache","id":"CVE-2023-22469","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":"Nextcloud Deck vulnerable to uncontrolled resource consumption","id":"CVE-2023-22470"},"packages":[],"prev":{"headline":"Discourse vulnerable to Cross-site Scripting in local oneboxes","id":"CVE-2023-22468"},"products":["security-advisories"],"published":"2023-01-10","related":[{"cvss_score":8.1,"headline":"Missing permission check on Deck API","id":"CVE-2021-39225","kev_date_added":null,"published":"2021-10-25"},{"cvss_score":8,"headline":"Missing authorization in Nextcloud Deck","id":"CVE-2020-8182","kev_date_added":null,"published":"2020-10-05"},{"cvss_score":6.5,"headline":"Circle can be accessed by non-Circle members in Nextcloud Deck","id":"CVE-2021-37631","kev_date_added":null,"published":"2021-09-07"},{"cvss_score":6.5,"headline":"Information disclosure in Nextcloud Deck","id":"CVE-2021-22913","kev_date_added":null,"published":"2021-06-11"},{"cvss_score":5.4,"headline":"Nextcloud Deck app allowed user with \"Can share\" permission to modify permissions of other non-owners","id":"CVE-2025-66557","kev_date_added":null,"published":"2025-12-05"},{"cvss_score":5,"headline":"Possibility for anyone to add a stack with existing tasks on anyone's board in Nextcloud Deck","id":"CVE-2022-29159","kev_date_added":null,"published":"2022-05-20"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-10","vendors":["nextcloud"]},"summary":"Unauthorized users can access cached preview data of Nextcloud Deck cards they lack permission to view, exposing sensitive information.","url":"https://insights.sbomify.com/CVE-2023-22469/"}