CVE-2026-7617PoC

LOWCVSS 5.3 · MEDIUM

Exploit discussion active in current signal (1 latest mentions)

Immediate actions

Hunt for exploitation attempts and persistence artifacts
Increase monitoring for publicly documented tradecraft
Track advisory updates for patch or workaround availability

Recommended action window: High priority (within 72h)

NVD description

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.

Back to dashboard

1.5/ 10 priority

Sources & remediation

Other references

Weakness type (CWE)

CWE-862

Priority

LOW

Exploitation

NONE

PoC

YES

Patch

NONE

Momentum

NONE

Threat summary

Public PoC is present in monitored signal
1 mentions across 1 observed day

What's happening

PoC mentioned or linked in 1 signal
Technical details provided in 1 signal
1 total mentions across 1 day

Deep dive

Activity timeline1 mentions / 1d

Signal classification1 categories

PoC

1100.0%

Referenced assets1 URL

By indicator

https://atomicedge.io/cve-proof/cve-2026-7617-wpoauth-version-1-0-7-medium-vulnerability-proof-of-concept

Full discourse1 post

Atomic Edge@atomicedgeWAF91d
PoC
https://atomicedge.io/cve-proof/cve-2026-7617-wpoauth-version-1-0-7-medium-vulnerability-proof-of-concept CVE-2026-7617 wpoauth (CVSS Score 5.3) #WordPress plugin #vulnerability #cybersecurity #wordpressfirewall #wordpresssecurity #hacking #wpsecurity #atomicedge #cybersecurit…
Post summary
The tweet references a proof‑of‑concept for CVE‑2026‑7617, a WordPress wpoauth plugin vulnerability with a CVSS score of 5.3, but does not detail exploitation code, active attacks, or available fixes.
0000051
11 followersView on X

Explore more

Back to dashboard