{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-26041 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-26041 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-26041 is a low-severity vulnerability in nextcloud security-advisories, published on 27 Feb 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-26041 and fix it if it is affected.\n\nWhat it is: CVE-2023-26041 is a low-severity vulnerability in nextcloud security-advisories, published on 27 Feb 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-26041 in the wild and no public exploit code.\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-26041/ (Markdown: https://insights.sbomify.com/CVE-2023-26041/index.md)","id":"CVE-2023-26041","markdown":"https://insights.sbomify.com/CVE-2023-26041/index.md","name":"CVE-2023-26041","record":{"aliases":["GHSA-j53p-r755-v4jf"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Nextcloud Talk","requires_auth":"low_privilege","summary":"Misconfigured cron jobs allow attackers to retrieve expired chat messages via the API, bypassing frontend visibility restrictions.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"nextcloud_talk","vendor":"nextcloud"}],"cvss":{"score":2.6,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-668","name":"Exposure of Resource to Wrong Sphere"},{"id":"CWE-359","name":"Exposure of Private Personal Information to an Unauthorized Actor"}],"description":"Nextcloud Talk is a fully on-premises audio/video and chat communication service. When cron jobs were misconfigured and therefore messages are not expired, the API would still return them while they were then hidden by the frontend code. It is recommended that the Nextcloud Talk is upgraded to 15.0.3. There are no workaround available.","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":"Nextcloud Talk messages can still be seen on conversation after expiring when cron is misconfigured","id":"CVE-2023-26041","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"HTML/XSS injection possibilities in Part-DB","id":"CVE-2023-26042"},"packages":[],"prev":{"headline":"Discourse chat messages susceptible to Cross-site Scripting through chat excerpts","id":"CVE-2023-26040"},"products":["security-advisories"],"published":"2023-02-27","related":[{"cvss_score":4.8,"headline":"Nextcloud Talk guests can continue to receive video streams from call after being removed from a conversation","id":"CVE-2022-41971","kev_date_added":null,"published":"2022-12-01"}],"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-03-10","vendors":["nextcloud"]},"summary":"Misconfigured cron jobs allow attackers to retrieve expired chat messages via the API, bypassing frontend visibility restrictions.","url":"https://insights.sbomify.com/CVE-2023-26041/"}