{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-77999 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-77999 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-77999 is a high-severity vulnerability in j2commerce.com J2Store extension for Joomla, published on 3 Sep 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-77999 and fix it if it is affected.\n\nWhat it is: CVE-2026-77999 is a high-severity vulnerability in j2commerce.com J2Store extension for Joomla, published on 3 Sep 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-77999 in the wild and no public exploit code.\n\nAffected product: j2commerce.com J2Store extension for Joomla. 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-77999/ (Markdown: https://insights.sbomify.com/CVE-2026-77999/index.md)","id":"CVE-2026-77999","markdown":"https://insights.sbomify.com/CVE-2026-77999/index.md","name":"CVE-2026-77999","record":{"aliases":["GHSA-ffqf-m6vh-866w"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Joomla e-commerce extension","requires_auth":"none","summary":"Attackers can forge PayPal callbacks to fraudulently confirm orders or fail others without payment due to flawed IPN validation logic.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Joomla","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-602","name":"Client-Side Enforcement of Server-Side Security"},{"id":"CWE-472","name":"External Control of Assumed-Immutable Web Parameter"}],"description":"Joomla Extension - j2commerce.com - Unauthenticated PayPal callback forgery leading to order confirmation fraud in J2Store 1.0.0-3.3.21, 4.0.0-4.0.21, 4.1.0-4.1.6 - The PayPal IPN listener's signature check (`_validateIPN()`) accepted `UNVERIFIED` and any non-`INVALID` response as valid, made its verification request with `CURLOPT_SSL_VERIFYPEER` disabled, and stored its verdict in a field nothing downstream ever checked — so processing continued regardless of the outcome. Separately, the paid-amount comparison only ran when `mc_gross` was a positive number; omitting the field from the POST body (`floatval(null) == 0`) skipped the check entirely. Combined with a merchant-configured `receiver_email` and a sequential, enumerable order id read from the `custom` field, an anonymous POST was enough to move a pending order straight to `CONFIRMED` with no payment, or force another customer's pending order to `FAILED`. `paypalv2.php` performed no amount check under any circumstances.","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":"Business logic in J2Store extension for Joomla","id":"CVE-2026-77999","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Joomla Extension - j2commerce.com - Open redirect in cart controller in J2Store 1.0.0-3.3.20, 4.0.0-4.0.20, 4.1.0-4.1.5","id":"CVE-2026-78000"},"packages":[],"prev":{"headline":"Auth bypass in SAML SP Single Sign On – Login with ADFS extension for Joomla","id":"CVE-2026-77998"},"products":["J2Store extension for Joomla"],"published":"2026-09-03","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-09-03","vendors":["j2commerce.com"]},"summary":"Attackers can forge PayPal callbacks to fraudulently confirm orders or fail others without payment due to flawed IPN validation logic.","url":"https://insights.sbomify.com/CVE-2026-77999/"}