{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-4839 exists.","fix":"No fix has been published for CVE-2025-4839 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-4839 is a low-severity vulnerability in itwanger paicoding, published on 17 May 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-4839 and fix it if it is affected.\n\nWhat it is: CVE-2025-4839 is a low-severity vulnerability in itwanger paicoding, published on 17 May 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-4839 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-4839/ (Markdown: https://insights.sbomify.com/CVE-2025-4839/index.md)","id":"CVE-2025-4839","markdown":"https://insights.sbomify.com/CVE-2025-4839/index.md","name":"CVE-2025-4839","record":{"aliases":["GHSA-vq5p-c2v7-53v5"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Java web application","requires_auth":"none","summary":"Attackers can bypass cross-domain restrictions in paicoding due to permissive CORS policies, potentially enabling unauthorized cross-origin requests.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"paicoding","vendor":"itwanger"}],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-942","name":"Permissive Cross-domain Security Policy with Untrusted Domains"},{"id":"CWE-346","name":"Origin Validation Error"}],"description":"A vulnerability has been found in itwanger paicoding 1.0.0/1.0.1/1.0.2/1.0.3 and classified as problematic. Affected by this vulnerability is an unknown functionality of the file /paicoding-core/src/main/java/com/github/paicoding/forum/core/util/CrossUtil.java. The manipulation leads to permissive cross-domain policy with untrusted domains. The attack can be launched remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. 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 CrossUtil.java cross-domain policy","id":"CVE-2025-4839","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Likes and Dislikes Plugin \u003c= 1.0.0 - Unauthenticated SQL Injection","id":"CVE-2025-4840"},"packages":[],"prev":{"headline":"kanwangzjm Funiture Login LoginServlet.java doPost redirect","id":"CVE-2025-4838"},"products":["paicoding"],"published":"2025-05-17","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 Browsing History home information disclosure","id":"CVE-2025-3966","kev_date_added":null,"published":"2025-04-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"}],"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-05-19","vendors":["itwanger"]},"summary":"Attackers can bypass cross-domain restrictions in paicoding due to permissive CORS policies, potentially enabling unauthorized cross-origin requests.","url":"https://insights.sbomify.com/CVE-2025-4839/"}