{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-14823 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-14823 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-14823 is a medium-severity vulnerability in ConnectWise ScreenConnect, published on 18 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-14823 and fix it if it is affected.\n\nWhat it is: CVE-2025-14823 is a medium-severity vulnerability in ConnectWise ScreenConnect, published on 18 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-14823 in the wild and no public exploit code.\n\nAffected product: ConnectWise ScreenConnect. 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-14823/ (Markdown: https://insights.sbomify.com/CVE-2025-14823/index.md)","id":"CVE-2025-14823","markdown":"https://insights.sbomify.com/CVE-2025-14823/index.md","name":"CVE-2025-14823","record":{"aliases":["GHSA-pxwx-c9g9-pm9p"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"ScreenConnect extension","requires_auth":"none","summary":"Unauthenticated users can retrieve encrypted configuration values via a client-facing endpoint in ScreenConnect's Certificate Signing Extension.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ConnectWise","cpe":[{"product":"screenconnect","vendor":"connectwise"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-201","name":"Insertion of Sensitive Information Into Sent Data"}],"description":"In deployments using the ScreenConnect™ Certificate Signing Extension, encrypted configuration values including an Azure Key Vault-related key, could be returned to unauthenticated users through a client-facing endpoint under certain conditions. The values remained encrypted and securely stored at rest; however, an encrypted representation could be exposed in client responses. Updating the Certificate Signing Extension to version 1.0.12 or higher ensures configuration handling occurs exclusively on the server side, preventing encrypted values from being transmitted to or rendered by client-side components.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Certificate Signing Extension Returns Encrypted Values","id":"CVE-2025-14823","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"** REJECT ** DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2025-14828"},"packages":[],"prev":{"headline":"DoS from quadratic complexity in model.ParseHashtags","id":"CVE-2025-14822"},"products":["ScreenConnect"],"published":"2025-12-18","related":[{"cvss_score":10,"headline":"ConnectWise ScreenConnect Authentication Bypass","id":"CVE-2024-1709","kev_date_added":"2024-02-22","published":"2024-02-21"},{"cvss_score":9.9,"headline":"ConnectWise ScreenConnect Improper Privilege Management and Missing Authorization","id":"CVE-2026-84869","kev_date_added":"2026-09-11","published":"2026-09-08"},{"cvss_score":8.4,"headline":"ConnectWise ScreenConnect Path Traversal","id":"CVE-2024-1708","kev_date_added":"2026-04-28","published":"2024-02-21"},{"cvss_score":8.1,"headline":"ConnectWise ScreenConnect Improper Authentication","id":"CVE-2025-3935","kev_date_added":"2025-06-02","published":"2025-04-25"},{"cvss_score":9.1,"headline":"Improper server-side validation in ScreenConnect extension framework","id":"CVE-2025-14265","kev_date_added":null,"published":"2025-12-11"},{"cvss_score":5.3,"headline":"ConnectWise - ScreenConnect Session Code Bypass","id":"CVE-2022-36781","kev_date_added":null,"published":"2022-09-28"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-18","vendors":["ConnectWise"]},"summary":"Unauthenticated users can retrieve encrypted configuration values via a client-facing endpoint in ScreenConnect's Certificate Signing Extension.","url":"https://insights.sbomify.com/CVE-2025-14823/"}