/

CVE-2026-86669

Severity:

HIGH RISK

(7.3)

Improper Authentication (CWE-287) in iWebShop Login

CVE-2026-86669

Deferred

Vulnerability type

Category:

Improper Authentication

CWE:

CWE-287

Impact:

Authentication Bypass and Unauthorized Access

Severity:

HIGH RISK

(7.3)

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.

Summary

A high-severity improper authentication vulnerability in iWebShop-5 affects the Login function in controllers/systemseller.php. A remote attacker may manipulate the Name argument to bypass intended authentication checks and gain unauthorized access, depending on the deployment and exposed login endpoint.

Affected context

The issue occurs in iWebShop-5 deployments using the affected system seller login functionality. Risk is higher when the login endpoint is remotely reachable and the Name argument is processed without reliably binding authentication decisions to verified credentials, account state, and authorization context.

Exploit preconditions

  • Attack surface: Remotely accessible system seller login endpoint
  • Required access: No legitimate authenticated account may be required if the authentication weakness can be triggered directly
  • Trigger point: Processing of the Name argument by the Login function
  • Why exploitation is possible: Authentication logic may accept manipulated identity data without adequately verifying the associated credentials or authorization state

Why this happens

The vulnerability is an improper authentication flaw mapped to CWE-287. The affected login logic appears to rely on user-controlled identity information in a way that can allow authentication decisions to be made without sufficient proof of identity. This insecure pattern weakens the separation between identifying an account and authenticating that account, potentially allowing unauthorized users to obtain an authenticated session.

Potential impact

  • An attacker may bypass login protections
  • Unauthorized users could access system seller functionality
  • Sensitive administrative or operational information may be exposed
  • Account or application data could be modified or deleted
  • Compromised access could support further attacks against the application

General mitigation guidance

Mitigation generally focuses on making authentication decisions depend only on independently verified credentials and server-side account state.

Common defensive patterns include:

  • Require strong server-side verification of credentials before creating an authenticated session
  • Treat identity-related request parameters as untrusted and avoid using them as proof of authentication
  • Bind sessions to verified principals and enforce authorization checks on every protected operation
  • Apply least privilege to system seller accounts and service identities
  • Use secure session handling, expiration, and invalidation controls
  • Add negative authentication tests for altered, missing, duplicated, and unexpected input values

How teams detect issues like this

Organizations can identify similar weaknesses through:

  • Static analysis and code review rules for authentication decisions based directly on request parameters
  • Review of login handlers for missing credential verification, weak session creation, or inconsistent authorization checks
  • Dynamic testing of authentication endpoints with altered identity fields and invalid credential combinations
  • Monitoring for successful logins without corresponding credential-verification events
  • Policy enforcement requiring centralized authentication and authorization components for protected functions
  • Neutral automated security review tools that flag CWE-287 patterns during development

Sources

SourceLink
github.comgithub.com/aircheng-org/iWebShop-5/
github.comgithub.com/aircheng-org/iWebShop-5/issues/6
vuldb.comvuldb.com/cve/CVE-2026-86669
vuldb.comvuldb.com/submit/908927
vuldb.comvuldb.com/vuln/399760
vuldb.comvuldb.com/vuln/399760/cti

Frequently asked

questions

Yes. The reported issue affects a remotely reachable login function, although practical exposure depends on whether that endpoint is accessible in the deployed environment.

The reported weakness may allow an attacker to bypass intended authentication, so a valid account may not be required. Actual access depends on deployment configuration and the behavior of the affected login flow.

Make session creation contingent on independently verified credentials and server-side account state, then enforce authorization checks for each protected operation.

Treat all identity-related request values as untrusted, centralize authentication logic, apply least privilege, and include negative tests and monitoring for anomalous authentication outcomes.

Find out what's already
exploitable in your codebase.