PatchTheCVEopen banking km vulnerabilities and fixes
Recent CVEs affecting open banking km, with upgrade or downgrade steps. 4 tracked.
Also searched as: openbankingkm.
open banking km has 4 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 0. Most recent: 2025-06-02. Highest priority: CVE-2024-6914 (score 53/100).
- CVE-2024-7097 MEDIUM 4.3 DOWNGRADE DOWNGRADE An incorrect authorization vulnerability exists in multiple WSO2 products due to a flaw in the SOAP admin serv
- CVE-2024-7096 MEDIUM 4.2 DOWNGRADE DOWNGRADE A privilege escalation vulnerability exists in multiple WSO2 products due to a business logic flaw in SOAP adm
- CVE-2024-7073 MEDIUM 6.5 DOWNGRADE DOWNGRADE A server-side request forgery (SSRF) vulnerability exists in multiple WSO2 products due to improper input vali
- CVE-2024-6914 CRITICAL 9.8 DOWNGRADE DOWNGRADE An incorrect authorization vulnerability exists in multiple WSO2 products due to a business logic flaw in the
FAQ
How do I fix open banking km vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is open banking km being exploited right now?
None of the tracked open banking km CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which open banking km CVE should I patch first?
CVE-2024-6914 currently ranks highest (53/100): An incorrect authorization vulnerability exists in multiple WSO2 products due to a business logic flaw in the .