{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-15511 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-15511 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-15511 is a medium-severity missing authorization vulnerability in Rupantorpay, published on 28 Jan 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-2025-15511 and fix it if it is affected.\n\nWhat it is: CVE-2025-15511 is a medium-severity missing authorization vulnerability in Rupantorpay, published on 28 Jan 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-2025-15511 in the wild and no public exploit code.\n\nAffected product: Rupantorpay. 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-2025-15511/ (Markdown: https://insights.sbomify.com/CVE-2025-15511/index.md)","id":"CVE-2025-15511","markdown":"https://insights.sbomify.com/CVE-2025-15511/index.md","name":"CVE-2025-15511","record":{"aliases":["GHSA-v47p-p4r6-wcwj"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can modify WooCommerce order statuses via the Rupantorpay plugin due to missing capability checks.","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-862","name":"Missing Authorization"}],"description":"The Rupantorpay plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the handle_webhook() function in all versions up to, and including, 2.0.0. This makes it possible for unauthenticated attackers to modify WooCommerce order statuses by sending crafted requests to the WooCommerce API endpoint.","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":"Rupantorpay \u003c= 2.0.0 - Missing Authorization to Unauthenticated Order Status Modification","id":"CVE-2025-15511","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Aplazo Payment Gateway \u003c= 1.4.3 - Missing Authorization to Unauthenticated Order Status Manipulation","id":"CVE-2025-15512"},"packages":[],"prev":{"headline":"Missing authorization in NEX-Forms – Ultimate Forms Plugin for WordPress","id":"CVE-2025-15510"},"products":["Rupantorpay"],"published":"2026-01-28","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":["rupantorpay"]},"summary":"Unauthenticated attackers can modify WooCommerce order statuses via the Rupantorpay plugin due to missing capability checks.","url":"https://insights.sbomify.com/CVE-2025-15511/"}