CVE-2026-9027

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

Score 5.3 from GitHub Security Advisory published 2026-07-09. A secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.3Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CorvusPay WooCommerce Payment Gateway plugin for WordPress is vulnerable to Payment Bypass via Improper Verification of Cryptographic Signature in all versions up to, and including, 2.7.4. The corvuspay_success_handler function registers the REST endpoint POST /wp-json/corvuspay/success/ with 'permission_callback' => '__return_true', and while it calls $this->client->validate->signature() and stores the boolean result in $res, the result is never evaluated in a conditional — it is only written to the debug log — causing execution to unconditionally reach $order->payment_complete() regardless of whether the cryptographic signature is valid. This makes it possible for unauthenticated attackers to mark any pending WooCommerce order as fully paid by sending a POST request to the success endpoint containing an arbitrary or forged signature value, allowing them to obtain goods or services without payment. Because WooCommerce order IDs are sequential integers, target orders are trivially enumerable via the order_number POST parameter, requiring no prior knowledge of the victim order.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
39
EG Risk 39/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
28th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 9, 2026

Last Modified

July 9, 2026

Vendor Advisories for CVE-2026-9027(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 177 total refreshes for this CVE.

  1. 2026-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:08 UTCEPSS rescore
  3. 2026-10-08 17:14 UTCEPSS rescore
  4. 2026-10-07 23:48 UTCEPSS rescore
  5. 2026-10-06 15:19 UTCEPSS rescore
  6. 2026-10-05 17:44 UTCEPSS rescore
  7. 2026-10-04 23:23 UTCEPSS rescore
  8. 2026-10-03 14:26 UTCEPSS rescore
  9. 2026-10-02 17:57 UTCEPSS rescore
  10. 2026-10-01 19:51 UTCEPSS rescore
  11. 2026-10-01 16:05 UTCEG score recompute
  12. 2026-10-01 16:04 UTCGHSA enrichment
  13. 2026-09-30 15:04 UTCEPSS rescore
  14. 2026-09-28 13:52 UTCEPSS rescore
  15. 2026-09-28 13:52 UTCEPSS rescore
  16. 2026-09-28 10:59 UTCEG score recompute
  17. 2026-09-28 10:59 UTCGHSA enrichment
  18. 2026-09-27 13:49 UTCEPSS rescore
  19. 2026-09-26 15:59 UTCEPSS rescore
  20. 2026-09-24 14:04 UTCEPSS rescore
  21. 2026-09-24 11:41 UTCEG score recompute
  22. 2026-09-24 11:41 UTCGHSA enrichment
  23. 2026-09-23 17:54 UTCEPSS rescore
  24. 2026-09-23 06:00 UTCEG score recompute
  25. 2026-09-23 06:00 UTCGHSA enrichment
Show 75 more
  1. 2026-09-22 16:01 UTCEPSS rescore
  2. 2026-09-21 21:09 UTCEPSS rescore
  3. 2026-09-20 20:16 UTCEPSS rescore
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 05:38 UTCEG score recompute
  6. 2026-09-18 05:38 UTCGHSA enrichment
  7. 2026-09-17 19:32 UTCEPSS rescore
  8. 2026-09-16 14:09 UTCEPSS rescore
  9. 2026-09-16 05:15 UTCEPSS rescore
  10. 2026-09-15 03:12 UTCEPSS rescore
  11. 2026-09-14 11:13 UTCEG score recompute
  12. 2026-09-14 11:13 UTCGHSA enrichment
  13. 2026-09-13 16:48 UTCEPSS rescore
  14. 2026-09-13 08:20 UTCEG score recompute
  15. 2026-09-13 08:20 UTCGHSA enrichment
  16. 2026-09-12 15:02 UTCEPSS rescore
  17. 2026-09-12 03:25 UTCEG score recompute
  18. 2026-09-12 03:25 UTCGHSA enrichment
  19. 2026-09-11 14:53 UTCEPSS rescore
  20. 2026-09-11 09:38 UTCEPSS rescore
  21. 2026-09-10 09:35 UTCEPSS rescore
  22. 2026-09-08 22:01 UTCEPSS rescore
  23. 2026-09-06 13:48 UTCEPSS rescore
  24. 2026-09-05 22:36 UTCEG score recompute
  25. 2026-09-05 22:36 UTCGHSA enrichment
  26. 2026-09-05 15:31 UTCEPSS rescore
  27. 2026-09-04 05:07 UTCEPSS rescore
  28. 2026-09-02 14:12 UTCEPSS rescore
  29. 2026-09-01 13:54 UTCEPSS rescore
  30. 2026-09-01 04:40 UTCEPSS rescore
  31. 2026-08-30 19:18 UTCEPSS rescore
  32. 2026-08-30 06:57 UTCEG score recompute
  33. 2026-08-30 06:57 UTCGHSA enrichment
  34. 2026-08-30 01:22 UTCEPSS rescore
  35. 2026-08-28 21:42 UTCEPSS rescore
  36. 2026-08-28 03:37 UTCEG score recompute
  37. 2026-08-28 03:37 UTCGHSA enrichment
  38. 2026-08-27 14:25 UTCEPSS rescore
  39. 2026-08-27 01:12 UTCEG score recompute
  40. 2026-08-27 01:12 UTCGHSA enrichment
  41. 2026-08-26 14:47 UTCEPSS rescore
  42. 2026-08-25 13:49 UTCEPSS rescore
  43. 2026-08-25 13:30 UTCEG score recompute
  44. 2026-08-25 13:30 UTCGHSA enrichment
  45. 2026-08-24 14:18 UTCEPSS rescore
  46. 2026-08-24 10:23 UTCEG score recompute
  47. 2026-08-24 10:23 UTCGHSA enrichment
  48. 2026-08-23 08:16 UTCEG score recompute
  49. 2026-08-23 08:16 UTCGHSA enrichment
  50. 2026-08-23 00:19 UTCEPSS rescore
  51. 2026-08-22 06:04 UTCEG score recompute
  52. 2026-08-22 06:04 UTCGHSA enrichment
  53. 2026-08-21 23:49 UTCEPSS rescore
  54. 2026-08-21 03:58 UTCEG score recompute
  55. 2026-08-21 03:58 UTCGHSA enrichment
  56. 2026-08-20 22:56 UTCEPSS rescore
  57. 2026-08-20 01:51 UTCEG score recompute
  58. 2026-08-20 01:51 UTCGHSA enrichment
  59. 2026-08-19 17:04 UTCEPSS rescore
  60. 2026-08-18 20:43 UTCEG score recompute
  61. 2026-08-18 20:43 UTCGHSA enrichment
  62. 2026-08-18 13:49 UTCEPSS rescore
  63. 2026-08-17 13:47 UTCEPSS rescore
  64. 2026-08-17 09:57 UTCEG score recompute
  65. 2026-08-17 09:57 UTCGHSA enrichment
  66. 2026-08-16 14:56 UTCEPSS rescore
  67. 2026-08-16 14:56 UTCEPSS rescore
  68. 2026-08-16 07:51 UTCEG score recompute
  69. 2026-08-16 07:51 UTCGHSA enrichment
  70. 2026-08-16 02:15 UTCEPSS rescore
  71. 2026-08-15 05:45 UTCEG score recompute
  72. 2026-08-15 05:45 UTCGHSA enrichment
  73. 2026-08-15 01:31 UTCEPSS rescore
  74. 2026-08-14 03:38 UTCEG score recompute
  75. 2026-08-14 03:38 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-9027?
CVE-2026-9027 is a medium vulnerability published on July 9, 2026. The CorvusPay WooCommerce Payment Gateway plugin for WordPress is vulnerable to Payment Bypass via Improper Verification of Cryptographic Signature in all versions up to, and including, 2.7.4. The corvuspaysuccesshandler function registers the REST endpoint POST /wp-json/corvuspay/success/ with…
When was CVE-2026-9027 disclosed?
CVE-2026-9027 was first published on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9027 actively exploited?
CVE-2026-9027 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-9027?
CVE-2026-9027 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-9027?
No fix for CVE-2026-9027 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-9027 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-9027

Explore →

Is Your Infrastructure Affected by CVE-2026-9027?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.