CVE-2026-7617

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-06-24. a secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

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

The Secufor_OAuth plugin for WordPress is vulnerable to unauthorized access in all versions up to, and including, 1.0.7. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to disconnect the WordPress site from its linked Secufor account by clearing the plugin's stored login token and user login configuration.

CVSS v3
5.3
EG Score
5.3(high)
EPSS
21.3%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 25, 2026

References (5)

Vendor Advisories for CVE-2026-7617(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 24× in last 7d / 42× 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.

  1. 2026-07-06 23:54 UTCEG score recompute
  2. 2026-07-06 23:54 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 22:33 UTCEG score recompute
  8. 2026-07-05 22:33 UTCGHSA enrichment
  9. 2026-07-05 02:31 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 21:17 UTCEG score recompute
  12. 2026-07-04 21:17 UTCGHSA enrichment
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-03 19:58 UTCEG score recompute
  16. 2026-07-03 19:58 UTCGHSA enrichment
  17. 2026-07-02 18:42 UTCEG score recompute
  18. 2026-07-02 18:42 UTCGHSA enrichment
  19. 2026-07-01 17:26 UTCEG score recompute
  20. 2026-07-01 17:26 UTCGHSA enrichment
  21. 2026-07-01 15:07 UTCEPSS rescore
  22. 2026-06-30 23:22 UTCEPSS rescore
  23. 2026-06-30 16:10 UTCEG score recompute
  24. 2026-06-30 16:10 UTCGHSA enrichment
  25. 2026-06-29 14:53 UTCEG score recompute
Show 17 more
  1. 2026-06-29 14:53 UTCGHSA enrichment
  2. 2026-06-29 14:06 UTCEPSS rescore
  3. 2026-06-28 14:07 UTCEPSS rescore
  4. 2026-06-28 13:36 UTCEG score recompute
  5. 2026-06-28 13:36 UTCGHSA enrichment
  6. 2026-06-28 04:56 UTCEPSS rescore
  7. 2026-06-27 12:20 UTCEG score recompute
  8. 2026-06-27 12:19 UTCGHSA enrichment
  9. 2026-06-27 03:08 UTCEPSS rescore
  10. 2026-06-26 11:03 UTCEG score recompute
  11. 2026-06-26 11:02 UTCGHSA enrichment
  12. 2026-06-25 13:50 UTCEPSS rescore
  13. 2026-06-25 08:50 UTCEG score recompute
  14. 2026-06-25 08:50 UTCGHSA enrichment
  15. 2026-06-24 14:05 UTCEPSS rescore
  16. 2026-06-24 07:34 UTCEG score recompute
  17. 2026-06-24 07:29 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-7617?
CVE-2026-7617 is a medium vulnerability published on June 24, 2026. The Secufor_OAuth plugin for WordPress is vulnerable to unauthorized access in all versions up to, and including, 1.0.7. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to disconnect the WordPress…
When was CVE-2026-7617 disclosed?
CVE-2026-7617 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-7617 actively exploited?
CVE-2026-7617 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 21.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-7617?
CVE-2026-7617 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-7617?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-7617, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-7617?

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

Start Free Scan →Browse All CVEs