{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-67809 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-67809 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-67809 is a medium-severity vulnerability in n/a, published on 15 Dec 2025. 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-2025-67809 and fix it if it is affected.\n\nWhat it is: CVE-2025-67809 is a medium-severity vulnerability in n/a, published on 15 Dec 2025. 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-2025-67809 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2025-67809/ (Markdown: https://insights.sbomify.com/CVE-2025-67809/index.md)","id":"CVE-2025-67809","markdown":"https://insights.sbomify.com/CVE-2025-67809/index.md","name":"CVE-2025-67809","record":{"aliases":["GHSA-4f5p-gq89-4wfh"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Zimbra Collaboration","requires_auth":"none","summary":"Hardcoded Flickr API credentials in Zimbra allow attackers to impersonate the application and access user data via OAuth.","user_interaction":"required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"collaboration","vendor":"zimbra"}],"cvss":{"score":4.7,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"An issue was discovered in Zimbra Collaboration (ZCS) 10.0 and 10.1. A hardcoded Flickr API key and secret are present in the publicly accessible Flickr Zimlet used by Zimbra Collaboration. Because these credentials are embedded directly in the Zimlet, any unauthorized party could retrieve them and misuse the Flickr integration. An attacker with access to the exposed credentials could impersonate the legitimate application and initiate valid Flickr OAuth flows. If a user is tricked into approving such a request, the attacker could gain access to the user s Flickr data. The hardcoded credentials have since been removed from the Zimlet code, and the associated key has been revoked.","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":"Hardcoded credentials in n/a","id":"CVE-2025-67809","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Path traversal in n/a","id":"CVE-2025-67810"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2025-67807"},"products":["n/a"],"published":"2025-12-15","related":[{"cvss_score":6.1,"headline":"Synacor Zimbra Collaboration Suite (ZCS) Cross-Site Scripting (XSS)","id":"CVE-2024-27443","kev_date_added":"2025-05-19","published":"2024-08-12"},{"cvss_score":9.8,"headline":"Privilege escalation in n/a","id":"CVE-2023-29381","kev_date_added":null,"published":"2023-07-06"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2023-29382","kev_date_added":null,"published":"2023-07-06"},{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2022-32294","kev_date_added":null,"published":"2022-07-11"},{"cvss_score":9.8,"headline":"Server-side request forgery in n/a","id":"CVE-2021-35209","kev_date_added":null,"published":"2021-07-02"},{"cvss_score":9.1,"headline":"Cross-site scripting in n/a","id":"CVE-2023-50808","kev_date_added":null,"published":"2024-02-13"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2023-34193","kev_date_added":null,"published":"2023-07-06"}],"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-12-15","vendors":["n/a"]},"summary":"Hardcoded Flickr API credentials in Zimbra allow attackers to impersonate the application and access user data via OAuth.","url":"https://insights.sbomify.com/CVE-2025-67809/"}