How broadly exploitable is this vulnerability?

The 2FA bypass is broadly exploitable wherever the LoginControl PGP 2FA is enabled and an attacker can obtain a user's public key; factoring 512-bit RSA is within reach of modest hardware. The resource exhaustion aspect is exploitable by any unauthenticated party with network access to the affected endpoints.

What level of access does an attacker need to exploit this?

For 2FA bypass, an attacker needs network access to the login interface and a way to obtain the victim's PGP public key. For CPU exhaustion, only unauthenticated HTTP access to the `generateKeys.json.php` and `encryptMessage.json.php` endpoints is required.

What is the safest general fix pattern?

Enforce strong, standards-aligned cryptographic parameters (e.g., RSA ≥ 2048 bits) in the code, invalidate or migrate weak keys, and require authentication plus rate limiting for any endpoints that perform heavyweight cryptographic operations.

Severity:

HIGH RISK

(7.4)

Insufficient RSA Key Strength (CWE-326) in WWBN AVideo PGP 2FA LoginControl Plugin

CVE-2026-33488

Published:

Mar 23, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

Insufficient Cryptographic Strength

CWE:

CWE-326

Impact:

Two-Factor Authentication Bypass and Resource Exhaustion

Severity:

HIGH RISK

(7.4)

CVSS Version:

3.1

Vulnerability Type

Category:

Insufficient Cryptographic Strength

CWE:

CWE-326

Impact:

Two-Factor Authentication Bypass and Resource Exhaustion

Severity:

HIGH RISK

(7.4)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Insufficient RSA Key Strength (CWE-326) in WWBN AVideo PGP 2FA LoginControl Plugin

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal