{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-49225 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-49225 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-49225 is a high-severity missing authorization vulnerability in givanz Vvveb, published on 18 Aug 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-49225 and fix it if it is affected.\n\nWhat it is: CVE-2026-49225 is a high-severity missing authorization vulnerability in givanz Vvveb, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-49225 in the wild and no public exploit code.\n\nAffected product: givanz Vvveb. 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-49225/ (Markdown: https://insights.sbomify.com/CVE-2026-49225/index.md)","id":"CVE-2026-49225","markdown":"https://insights.sbomify.com/CVE-2026-49225/index.md","name":"CVE-2026-49225","record":{"aliases":["GHSA-gmrp-ccwf-xggq"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Vvveb CMS","requires_auth":"low_privilege","summary":"A low-privileged Vendor can read, restore, or delete other Vendors' product revisions due to missing authorization checks in the revision controller.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"Vvveb is a powerful and easy to use CMS with page builder to build websites, blogs or ecommerce stores. Prior to 1.0.8.4, Vvveb backend product revision operations allow a low-privileged Vendor to access revisions for products owned by another Vendor. The admin/controller/product/revisions.php route reuses admin/controller/content/revisions.php, while admin/sql/sqlite/product_content_revision.sql trusts caller-controlled product_id, language_id, and created_at values without applying the current admin_id to revision reads, restores, and deletes. An attacker can read historic product content, restore a revision over another Vendor's live product content, or delete revision records, exposing private copy, corrupting product pages, and removing audit history. This issue is fixed in version 1.0.8.4.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Vvveb product revision authorization bypass allows Vendors to read, restore, or delete other Vendors' product revisions","id":"CVE-2026-49225","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Vvveb post authorization bypass allows Authors to view, duplicate, or delete other Authors' posts","id":"CVE-2026-49226"},"packages":[],"prev":{"headline":"Vvveb post revision authorization bypass allows Authors to read, restore, or delete other Authors' post revisions","id":"CVE-2026-49224"},"products":["Vvveb"],"published":"2026-08-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-18","vendors":["givanz"]},"summary":"A low-privileged Vendor can read, restore, or delete other Vendors' product revisions due to missing authorization checks in the revision controller.","url":"https://insights.sbomify.com/CVE-2026-49225/"}