/

CVE-2026-86665

Severity:

HIGH RISK

(7.3)

Missing Authorization (CWE-862) in iWebShop-5 Update

CVE-2026-86665

Deferred

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-862, CWE-863

Impact:

Unauthorized access or modification of application resources

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 missing authorization vulnerability in iWebShop-5 affects the Update::index function in controllers/update.php. A remote attacker may invoke the affected functionality without the required permission checks, potentially performing update-related actions that should be restricted.

Affected context

The issue occurs in iWebShop-5 deployments where the update controller is reachable through a remote request and authorization is not consistently enforced before the Update::index operation executes. The practical impact depends on the resources and actions exposed by that controller and the privileges normally expected for the affected workflow.

Exploit preconditions

  • Attack surface: The remotely accessible update controller endpoint
  • Required access: Network access to the affected iWebShop-5 application; valid authentication may not be required if the endpoint is exposed without an effective authorization check
  • Trigger point: A request reaching Update::index in controllers/update.php
  • Why exploitation is possible: The operation may process requests without verifying whether the caller has the permissions required to perform the requested action

Why this happens

The underlying bug is an authorization-control failure. The affected controller appears to allow a security-sensitive operation to proceed without reliably checking the caller's permissions for that specific resource or action. This maps primarily to CWE-862: Missing Authorization and is also related to CWE-863: Incorrect Authorization, because authorization enforcement may be absent or improperly applied at the operation boundary.

Potential impact

  • An unauthenticated or low-privileged remote user may perform restricted update operations
  • Application data or configuration may be modified without authorization
  • Security controls or business workflows may be bypassed
  • The application may experience integrity loss or unauthorized administrative changes
  • Follow-on compromise could occur if modified resources influence other privileged processes

General mitigation guidance

Mitigation generally focuses on enforcing authorization at the server-side operation boundary rather than relying on hidden interfaces, client-side checks, or route assumptions.

Common defensive patterns include:

  • Require explicit permission checks before every sensitive update action
  • Apply deny-by-default authorization policies for controller endpoints
  • Validate both the caller's role and access to the specific target resource
  • Avoid trusting client-supplied identifiers, roles, or privilege indicators
  • Separate administrative update functions from publicly reachable routes
  • Run application components with only the privileges required for their defined tasks
  • Record and review denied and successful authorization decisions

How teams detect issues like this

Organizations commonly assess missing-authorization risks through:

  • Static analysis for controller actions that modify state without nearby authorization checks
  • Code review of route-to-controller mappings and permission middleware
  • Tests that exercise sensitive endpoints with unauthenticated and lower-privileged identities
  • Dynamic access-control testing that compares responses across user roles
  • Policy enforcement requiring explicit authorization annotations or middleware for state-changing operations
  • Monitoring for unexpected update requests, privilege-boundary violations, and repeated authorization failures

Sources

SourceLink
github.comgithub.com/aircheng-org/iWebShop-5/
github.comgithub.com/aircheng-org/iWebShop-5/issues/2
vuldb.comvuldb.com/cve/CVE-2026-86665
vuldb.comvuldb.com/submit/908923
vuldb.comvuldb.com/vuln/399756
vuldb.comvuldb.com/vuln/399756/cti

Frequently asked

questions

Yes. The described attack surface is a remotely reachable update function, although exposure depends on the application's routing, network access, and deployment configuration.

Not necessarily. The central issue is the absence or failure of an effective authorization check, so the exact requirement depends on any authentication and routing controls surrounding the affected function.

Enforce server-side, deny-by-default authorization for the update operation and verify both the caller's privilege and access to the specific resource being changed.

Use centralized authorization middleware, require explicit permission checks for state-changing handlers, test endpoints with multiple privilege levels, and monitor authorization decisions in production.

Find out what's already
exploitable in your codebase.