{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35183 exists.","fix":"No fix has been published for CVE-2026-35183 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-35183 is a high-severity missing authorization vulnerability in Ajax30 BraveCMS-2.0, published on 6 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-35183 and fix it if it is affected.\n\nWhat it is: CVE-2026-35183 is a high-severity missing authorization vulnerability in Ajax30 BraveCMS-2.0, published on 6 Apr 2026. 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-2026-35183 exists.\n\nAffected product: Ajax30 BraveCMS-2.0. 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-2026-35183/ (Markdown: https://insights.sbomify.com/CVE-2026-35183/index.md)","id":"CVE-2026-35183","markdown":"https://insights.sbomify.com/CVE-2026-35183/index.md","name":"CVE-2026-35183","record":{"aliases":[],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Brave CMS","requires_auth":"low_privilege","summary":"Authenticated users can delete images belonging to other users' articles due to missing ownership checks in the image deletion endpoint.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"bravecms","vendor":"ajax30"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"Brave CMS is an open-source CMS. Prior to 2.0.6, an Insecure Direct Object Reference (IDOR) vulnerability exists in the article image deletion feature. It is located in app/Http/Controllers/Dashboard/ArticleController.php within the deleteImage method. The endpoint accepts a filename from the URL but does not verify ownership. This allows an authenticated user with edit permissions to delete images attached to articles owned by other users. This vulnerability is fixed in 2.0.6.","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":"Brave CMS has an Insecure Direct Object Reference in Article Image Deletion","id":"CVE-2026-35183","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"EcclesiaCRM has a Critical SQL Injection","id":"CVE-2026-35184"},"packages":[],"prev":{"headline":"Missing Authorization Privilege Escalation","id":"CVE-2026-35182"},"products":["BraveCMS-2.0"],"published":"2026-04-06","related":[{"cvss_score":9.3,"headline":"Brave CMS has Unrestricted File Upload in BraveCMS via CKEditor Endpoint","id":"CVE-2026-35047","kev_date_added":null,"published":"2026-04-06"},{"cvss_score":8.8,"headline":"Brave CMS Sffected by Unrestricted File Upload via CKEditor Endpoint","id":"CVE-2026-35164","kev_date_added":null,"published":"2026-04-06"},{"cvss_score":8.8,"headline":"Missing Authorization Privilege Escalation","id":"CVE-2026-35182","kev_date_added":null,"published":"2026-04-06"}],"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-04-07","vendors":["Ajax30"]},"summary":"Authenticated users can delete images belonging to other users' articles due to missing ownership checks in the image deletion endpoint.","url":"https://insights.sbomify.com/CVE-2026-35183/"}