CVE-2026-12877

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-24. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-48492 (ENISA EUVD) · GHSA-6v2p-hv27-r8xg (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.1Exploit: No code on recordExposed services: Not assessed

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

The CVE record's CNA (WPScan) lists Project Management, Bug and Issue Tracking Plugin versions before 5.1.0 as affected. No release containing a fix is confirmed on record.

The Project Management, Bug and Issue Tracking Plugin WordPress plugin before 5.1.0 does not sanitise and escape user supplied input before using it in a SQL query, allowing unauthenticated attackers to perform SQL injection attacks. This is exploitable in the Project Management, Bug and Issue Tracking Plugin WordPress plugin before 5.1.0's standard front-end issue-tracker configuration.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
72
EG Risk 72/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
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
35th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

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 public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 24, 2026

Last Modified

July 24, 2026

Advisory Details (1)

Auto-updated Sep 16, 2026
No fix on record yet.
Web page

Software Issue Manager < 5.1.0 – Unauthenticated SQL Injection via Search Parameter | CVE 2026-12877 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/e9d0ea92-1046-457b-9619-38b61848e36a/

Vendor Advisories for CVE-2026-12877(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 22× in last 7d / 77× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 447 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 347 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-12877?
CVE-2026-12877 is a critical-severity vulnerability; its CVE record was published on July 24, 2026. The Project Management, Bug and Issue Tracking Plugin WordPress plugin before 5.1.0 does not sanitise and escape user supplied input before using it in a SQL query, allowing unauthenticated attackers to perform SQL injection attacks. This is exploitable in the Project Management, Bug and Issue…
When was the CVE record for CVE-2026-12877 published?
The CVE record for CVE-2026-12877 was published on July 24, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 24, 2026; the record at its source may have been updated since.
Is CVE-2026-12877 actively exploited?
CVE-2026-12877 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-12877?
CVE-2026-12877 has a CVSS v3.1 base score of 9.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-12877?
No fix for CVE-2026-12877 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 CVE record's CNA (WPScan) lists Project Management, Bug and Issue Tracking Plugin versions before 5.1.0 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-12877 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-12877?

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