{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73314 exists.","fix":"No fix has been published for CVE-2026-73314 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-73314 is a high-severity vulnerability in XenForo, published on 8 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-73314 and fix it if it is affected.\n\nWhat it is: CVE-2026-73314 is a high-severity vulnerability in XenForo, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73314 exists.\n\nAffected product: XenForo. 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-73314/ (Markdown: https://insights.sbomify.com/CVE-2026-73314/index.md)","id":"CVE-2026-73314","markdown":"https://insights.sbomify.com/CVE-2026-73314/index.md","name":"CVE-2026-73314","record":{"aliases":["GHSA-rqwm-9m4j-f7g3"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"XenForo forum software","requires_auth":"none","summary":"Unauthenticated attackers can bypass PayPal webhook signature verification in XenForo, allowing them to process fabricated payment events.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"xenforo","vendor":"xenforo"}],"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-754","name":"Improper Check for Unusual or Exceptional Conditions"}],"description":"XenForo before 2.3.13 contains a signature verification logic error in the PayPal REST webhook handler that allows unauthenticated attackers to bypass payment signature validation by submitting a webhook request with an unsupported auth_algo header value. When the algorithm cannot be mapped to a supported hash function, the verification function incorrectly returns true instead of failing, causing the caller to treat the fabricated request as verified and process the payment event without a valid PayPal signature.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-09-08","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-09-08T16:35:24Z","kind":"github_poc","ref":"https://github.com/BomboBombone/CVE-2026-73314","stars":0,"title":"Sanitized XenForo write-up and proof of concept for CVE-2026-73314."}],"tier":"weaponised"},"has_fix":null,"headline":"XenForo \u003c 2.3.13 Signature Verification Bypass via PayPal REST Webhook","id":"CVE-2026-73314","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"XenForo \u003c 2.3.13 SSRF via PayPal REST Webhook Handler","id":"CVE-2026-73315"},"packages":[],"prev":{"headline":"XenForo \u003c 2.3.13 MFA Bypass via Passkey TFA Provider","id":"CVE-2026-73313"},"products":["XenForo"],"published":"2026-09-08","related":[{"cvss_score":9.3,"headline":"XenForo Passkey Security Bypass","id":"CVE-2025-71279","kev_date_added":null,"published":"2026-04-01"},{"cvss_score":9.1,"headline":"XenForo \u003c 2.3.13 Authentication Bypass via OAuth2 Token Endpoint","id":"CVE-2026-73309","kev_date_added":null,"published":"2026-09-08"},{"cvss_score":9.1,"headline":"XenForo \u003c 2.3.13 OAuth2 Authorization Code Reuse","id":"CVE-2026-73311","kev_date_added":null,"published":"2026-09-08"},{"cvss_score":9.1,"headline":"XenForo \u003c 2.3.13 Refresh Token Replay via Expired Access Token","id":"CVE-2026-73312","kev_date_added":null,"published":"2026-09-08"},{"cvss_score":8.8,"headline":"Xenforo before 2.2.16 allows CSRF.","id":"CVE-2024-38457","kev_date_added":null,"published":"2024-06-16"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2024-38458","kev_date_added":null,"published":"2024-06-16"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-01","vendors":["XenForo"]},"summary":"Unauthenticated attackers can bypass PayPal webhook signature verification in XenForo, allowing them to process fabricated payment events.","url":"https://insights.sbomify.com/CVE-2026-73314/"}