{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3966 exists.","fix":"No fix has been published for CVE-2025-3966 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-3966 is a medium-severity vulnerability in itwanger paicoding, published on 27 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-3966 and fix it if it is affected.\n\nWhat it is: CVE-2025-3966 is a medium-severity vulnerability in itwanger paicoding, published on 27 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3966 exists.\n\nAffected product: itwanger paicoding. 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-3966/ (Markdown: https://insights.sbomify.com/CVE-2025-3966/index.md)","id":"CVE-2025-3966","markdown":"https://insights.sbomify.com/CVE-2025-3966/index.md","name":"CVE-2025-3966","record":{"aliases":["GHSA-jr28-crcf-pgh6"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"paicoding web application","requires_auth":"low_privilege","summary":"Remote attackers can access browsing history information via the user home endpoint, exposing sensitive user data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"paicoding","vendor":"itwanger"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"A vulnerability was found in itwanger paicoding 1.0.3 and classified as problematic. Affected by this issue is some unknown functionality of the file /user/home?userId=1\u0026homeSelectType=read of the component Browsing History Handler. The manipulation leads to information disclosure. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.","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":"itwanger paicoding Browsing History home information disclosure","id":"CVE-2025-3966","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"itwanger paicoding Article post improper authorization","id":"CVE-2025-3967"},"packages":[],"prev":{"headline":"itwanger paicoding post cross site scripting","id":"CVE-2025-3965"},"products":["paicoding"],"published":"2025-04-27","related":[{"cvss_score":5.3,"headline":"itwanger paicoding Image Save Endpoint ImageRestController.java save server-side request forgery","id":"CVE-2026-3286","kev_date_added":null,"published":"2026-02-27"},{"cvss_score":5.3,"headline":"itwanger paicoding Article post improper authorization","id":"CVE-2025-3967","kev_date_added":null,"published":"2025-04-27"},{"cvss_score":5.1,"headline":"itwanger paicoding post cross site scripting","id":"CVE-2025-3965","kev_date_added":null,"published":"2025-04-27"},{"cvss_score":2.3,"headline":"itwanger paicoding CrossUtil.java cross-domain policy","id":"CVE-2025-4839","kev_date_added":null,"published":"2025-05-17"}],"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-04-28","vendors":["itwanger"]},"summary":"Remote attackers can access browsing history information via the user home endpoint, exposing sensitive user data.","url":"https://insights.sbomify.com/CVE-2025-3966/"}