LiveActive security incident?Get immediate response
CVE Record

CVE-2023-49810: A login attempt restriction bypass vulnerability exists in the checkLoginAttempts functionality of WWBN AVi...

A login attempt restriction bypass vulnerability exists in the checkLoginAttempts functionality of WWBN AVideo dev master commit 15fed957fb. A specially crafted HTTP request can lead to captcha bypass, which can be abused by an attacker to brute force user credentials. An attacker can send a series of HTTP requests to trigger this vulnerability.

HighCVSS 7.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

WWBN AVideo had a flaw that could let attackers bypass the captcha tied to login-attempt restrictions. That makes password guessing more practical against affected deployments. The cited affected version is only dev master commit 15fed957fb; the bundle does not prove broader release exposure.

Executive priority

Prioritize review if AVideo is externally exposed or protects privileged media, admin, or customer accounts. The main business risk is account takeover through easier password guessing.

Technical view

CVE-2023-49810 is a CWE-307 improper login-attempt restriction issue in AVideo checkLoginAttempts. A specially crafted HTTP request can bypass captcha and support brute-force credential attacks. CVSS 3.1 is 7.3 with network, low-complexity, unauthenticated exploitation characteristics.

Likely exposure

Exposure is limited by the provided evidence to WWBN AVideo dev master commit 15fed957fb, especially where the login interface is reachable from the internet or untrusted networks.

Exploitation context

The bundle describes abuse through repeated HTTP requests, but KEV is false and no provided source confirms active exploitation. Treat as plausible credential-attack enablement, not confirmed in-the-wild compromise.

Researcher notes

Evidence supports an unauthenticated, network-reachable captcha bypass in checkLoginAttempts, mapped to CWE-307. The source bundle does not provide a fixed version, patch commit, exploitation telemetry, or evidence beyond the named dev commit.

Mitigation direction

  • Identify whether any AVideo deployment is based on dev master commit 15fed957fb.
  • Check WWBN AVideo and Talos guidance for an upstream fix or secure version.
  • Restrict public access to AVideo login pages where business requirements allow.
  • Monitor and rate-limit repeated login attempts at edge controls.
  • Review authentication protections, including captcha, lockout, MFA, and alerting.

Validation and detection

  • Inventory AVideo instances and compare deployed code or version lineage to commit 15fed957fb.
  • Review authentication logs for repeated failed logins and captcha anomalies.
  • Confirm whether vendor guidance names a fixed commit or release before upgrading.
  • Validate login-attempt controls in an authorized test environment without credential spraying.
  • Check whether internet-facing AVideo login routes are reachable from untrusted networks.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-307: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-49810 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.3CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L3.93.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.3High
CVSS 3.1 vector shape for CVE-2023-49810Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
WWBNAVideodev master commit 15fed957fbListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-307 · source CWE mapping

Improper Restriction of Excessive Authentication Attempts

Improper Restriction of Excessive Authentication Attempts represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.