{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-44039 exists.","fix":"No fix has been published for CVE-2025-44039 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-44039 is a medium-severity vulnerability in n/a, published on 13 May 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-44039 and fix it if it is affected.\n\nWhat it is: CVE-2025-44039 is a medium-severity vulnerability in n/a, published on 13 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-44039 exists.\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-44039/ (Markdown: https://insights.sbomify.com/CVE-2025-44039/index.md)","id":"CVE-2025-44039","markdown":"https://insights.sbomify.com/CVE-2025-44039/index.md","name":"CVE-2025-44039","record":{"aliases":["GHSA-pwv6-v269-632r"],"analysis":{"component_type":"hardware_firmware","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"4G Router Firmware","requires_auth":"none","summary":"Local attackers can access the UART console without authentication to read boot sequences and reveal sensitive system information.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cp-xr-de21-s_firmware","vendor":"cpplusworld"}],"cvss":{"score":5.1,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"CP-XR-DE21-S -4G Router Firmware version 1.031.022 was discovered to contain insecure protections for its UART console. This vulnerability allows local attackers to connect to the UART port via a serial connection, read all boot sequence, and revealing internal system details and sensitive information without any authentication.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-05-02","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-05-02T21:20:47Z","kind":"github_poc","ref":"https://github.com/Yashodhanvivek/CP-XR-DE21-S--4G-Router-Vulnerabilities","stars":0,"title":"This report is for CVE-2025-44039 reserved for Router UART vulnerability assigned to Discoverer Yashodhan Vivek Mandke. Please download the report pdf in this repositoy"}],"tier":"weaponised"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2025-44039","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":"Auth bypass in n/a","id":"CVE-2025-44040"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2025-44034"},"products":["n/a"],"published":"2025-05-13","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-13","vendors":["n/a"]},"summary":"Local attackers can access the UART console without authentication to read boot sequences and reveal sensitive system information.","url":"https://insights.sbomify.com/CVE-2025-44039/"}