{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63293 exists.","fix":"No fix has been published for CVE-2025-63293 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-63293 is a medium-severity missing authorization vulnerability in n/a, published on 3 Nov 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-63293 and fix it if it is affected.\n\nWhat it is: CVE-2025-63293 is a medium-severity missing authorization vulnerability in n/a, published on 3 Nov 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-63293 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-63293/ (Markdown: https://insights.sbomify.com/CVE-2025-63293/index.md)","id":"CVE-2025-63293","markdown":"https://insights.sbomify.com/CVE-2025-63293/index.md","name":"CVE-2025-63293","record":{"aliases":["GHSA-jpw9-952g-5qcp"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Project Manager CRM","requires_auth":"low_privilege","summary":"Authenticated users can modify tickets they lack authorization for due to missing checks in the API.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"rise_ultimate_project_manager","vendor":"fairsketch"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"FairSketch Rise Ultimate Project Manager \u0026 CRM 3.9.4 is vulnerable to Insecure Permissions. A remote authenticated user can append comments or upload attachments to tickets for which they lack view or edit authorization, due to missing authorization checks in the ticketing/commenting API.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Missing authorization in n/a","id":"CVE-2025-63293","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in n/a","id":"CVE-2025-63294"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2025-63292"},"products":["n/a"],"published":"2025-11-03","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2017-17999","kev_date_added":null,"published":"2018-01-23"},{"cvss_score":8.1,"headline":"Cross-site scripting in n/a","id":"CVE-2025-60378","kev_date_added":null,"published":"2025-10-10"},{"cvss_score":6.9,"headline":"CodeCanyon RISE Ultimate Project Manager signin redirect","id":"CVE-2024-0545","kev_date_added":null,"published":"2024-01-15"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2025-56807","kev_date_added":null,"published":"2025-09-29"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2017-11181","kev_date_added":null,"published":"2017-07-12"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2017-11182","kev_date_added":null,"published":"2017-07-12"}],"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":"2026-07-05","vendors":["n/a"]},"summary":"Authenticated users can modify tickets they lack authorization for due to missing checks in the API.","url":"https://insights.sbomify.com/CVE-2025-63293/"}