{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-51503 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-51503 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-51503 is a medium-severity missing authorization vulnerability in Automattic WooPayments – Fully Integrated Solution Built and Supported by Woo, published on 31 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-51503 and fix it if it is affected.\n\nWhat it is: CVE-2023-51503 is a medium-severity missing authorization vulnerability in Automattic WooPayments – Fully Integrated Solution Built and Supported by Woo, published on 31 Dec 2023. 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-2023-51503 in the wild and no public exploit code.\n\nAffected product: Automattic WooPayments – Fully Integrated Solution Built and Supported by Woo. 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-2023-51503/ (Markdown: https://insights.sbomify.com/CVE-2023-51503/index.md)","id":"CVE-2023-51503","markdown":"https://insights.sbomify.com/CVE-2023-51503/index.md","name":"CVE-2023-51503","record":{"aliases":["GHSA-mg36-6hj2-xj8q"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress WooCommerce Payments","requires_auth":"none","summary":"Attackers can bypass authorization checks to access or modify other users' payment data via insecure direct object references.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[{"product":"woopayments","vendor":"automattic"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"Authorization Bypass Through User-Controlled Key vulnerability in Automattic WooPayments – Fully Integrated Solution Built and Supported by Woo.This issue affects WooPayments – Fully Integrated Solution Built and Supported by Woo: from n/a through 6.9.2.","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":"WordPress WooCommerce Payments Plugin \u003c= 6.6.2 is vulnerable to Insecure Direct Object References (IDOR)","id":"CVE-2023-51503","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress Dan's Embedder for Google Calendar Plugin \u003c= 1.2 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-51504"},"packages":[],"prev":{"headline":"WordPress WooCommerce Stripe Payment Gateway Plugin \u003c= 7.6.1 is vulnerable to Insecure Direct Object References (IDOR)","id":"CVE-2023-51502"},"products":["WooPayments – Fully Integrated Solution Built and Supported by Woo"],"published":"2023-12-31","related":[{"cvss_score":7.6,"headline":"WordPress WooCommerce Payments Plugin \u003c= 5.9.0 is vulnerable to SQL Injection","id":"CVE-2023-35915","kev_date_added":null,"published":"2023-12-20"},{"cvss_score":7.5,"headline":"WordPress WooCommerce Payments Plugin \u003c= 5.9.0 is vulnerable to Insecure Direct Object References (IDOR)","id":"CVE-2023-35916","kev_date_added":null,"published":"2023-12-20"},{"cvss_score":6.5,"headline":"WordPress WooCommerce Payments Plugin \u003c= 6.4.2 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-49828","kev_date_added":null,"published":"2023-12-14"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-28","vendors":["Automattic"]},"summary":"Attackers can bypass authorization checks to access or modify other users' payment data via insecure direct object references.","url":"https://insights.sbomify.com/CVE-2023-51503/"}