{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-3641 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-3641 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-3641 is a medium-severity missing authorization vulnerability in appmaxplataforma Appmax, published on 21 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-3641 and fix it if it is affected.\n\nWhat it is: CVE-2026-3641 is a medium-severity missing authorization vulnerability in appmaxplataforma Appmax, published on 21 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-3641 in the wild and no public exploit code.\n\nAffected product: appmaxplataforma Appmax. 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-3641/ (Markdown: https://insights.sbomify.com/CVE-2026-3641/index.md)","id":"CVE-2026-3641","markdown":"https://insights.sbomify.com/CVE-2026-3641/index.md","name":"CVE-2026-3641","record":{"aliases":["GHSA-crgh-3rc5-vq96"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["data_modify","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can manipulate WooCommerce order statuses, create arbitrary orders and products, and modify metadata via an unsecured webhook endpoint.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"The Appmax plugin for WordPress is vulnerable to Improper Input Validation in all versions up to, and including, 1.0.3. This is due to the plugin registering a public REST API webhook endpoint at /webhook-system without implementing webhook signature validation, secret verification, or any mechanism to authenticate that incoming webhook requests genuinely originate from the legitimate Appmax payment service. The plugin directly processes untrusted attacker-controlled input from the 'event' and 'data' parameters without verifying the webhook's authenticity. This makes it possible for unauthenticated attackers to craft malicious webhook payloads that can modify the status of existing WooCommerce orders (e.g., changing them to processing, refunded, cancelled, or pending), create entirely new WooCommerce orders with arbitrary data, create new WooCommerce products with attacker-controlled names/descriptions/prices, and write arbitrary values to order post metadata by spoofing legitimate webhook events.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Appmax \u003c= 1.0.3 - Missing Authorization to Order Status Manipulation and Arbitrary Order Creation via Webhook Endpoint","id":"CVE-2026-3641","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":9,"next":{"headline":"e-shot \u003c= 1.0.2 - Missing Authorization to Authenticated (Subscriber+) Form Settings Modification via AJAX","id":"CVE-2026-3642"},"packages":[],"prev":{"headline":"STRABL \u003c= 4.5 - Unauthenticated Arbitrary Webhook Creation via REST API Endpoint","id":"CVE-2026-3640"},"products":["Appmax"],"published":"2026-03-21","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["appmaxplataforma"]},"summary":"Unauthenticated attackers can manipulate WooCommerce order statuses, create arbitrary orders and products, and modify metadata via an unsecured webhook endpoint.","url":"https://insights.sbomify.com/CVE-2026-3641/"}