Skip to main content
Vulnerability Database/CVE-2026-112294

CVE-2026-112294: FlyCms Authorization Bypass Vulnerability

CVE-2026-112294 is an authorization bypass flaw in FlyCms that allows authenticated users to modify other users' content without proper ownership verification. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-112294 Overview

CVE-2026-112294 is a missing authorization vulnerability in FlyCms through commit edfdf724. The flaw resides in the ActionService.counter() method, where the checkRowOwner routine fails to verify row ownership. Any authenticated user can modify content rows belonging to other users by sending requests to /ucenter/action/{modelCode}/{id}/counter or /ucenter/action/compose. Attackers can add arbitrary deltas to numeric fields such as price, stock, or points, enabling data tampering across the application. The weakness maps to CWE-639: Authorization Bypass Through User-Controlled Key.

Critical Impact

Any registered FlyCms user can tamper with other users' numeric content fields, including prices, stock counts, and points, by invoking the vulnerable counter endpoints.

Affected Products

  • FlyCms content management system
  • All builds through commit edfdf724c3b944310f60c29aa755d03a00a75837
  • Deployments exposing /ucenter/action/* endpoints to registered users

Discovery Timeline

  • 2026-10-19 - CVE-2026-112294 published to NVD
  • 2026-10-19 - Last updated in NVD database

Technical Details for CVE-2026-112294

Vulnerability Analysis

FlyCms exposes action endpoints under /ucenter/action/ for incrementing or decrementing numeric fields on user-generated content. The ActionService.counter() method processes these requests and is intended to restrict modifications to rows owned by the requesting user. The service calls a helper named checkRowOwner, but the helper never compares the row's owner identifier against the authenticated principal. As a result, the authorization check is effectively a no-op. Any user with valid credentials can target records belonging to any other user and alter their values. The impact centers on integrity of business-critical numeric fields rather than confidentiality or availability.

Root Cause

The root cause is an incomplete access control implementation in the checkRowOwner function within ActionService.java. The function is invoked at the correct point in the request flow, yet it does not resolve the row's owner column or compare it to the session user. This matches the [CWE-639] pattern of authorization bypass through a user-controlled key, where the object identifier submitted by the client is honored without a server-side ownership check.

Attack Vector

Exploitation requires only a low-privileged authenticated account. The attacker submits an HTTP request to /ucenter/action/{modelCode}/{id}/counter or /ucenter/action/compose, specifying the target id, the field to modify (such as price, stock, or points), and a signed delta. The server performs the update without validating ownership, so the attacker can inflate point balances, deplete stock, or distort pricing on any content row. See the VulnCheck Advisory for FlyCms and the ActionService source for the vulnerable code path.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-112294

Indicators of Compromise

  • Unexpected changes to numeric columns such as price, stock, or points on content rows the owning user did not modify.
  • HTTP access log entries showing requests to /ucenter/action/{modelCode}/{id}/counter or /ucenter/action/compose from accounts that do not own the referenced id.
  • Spikes in counter endpoint traffic from a single authenticated session targeting many distinct content identifiers.

Detection Strategies

  • Correlate application access logs with the database owner column for each modified row and flag mismatches between the authenticated user and the row owner.
  • Deploy a web application firewall rule that inspects /ucenter/action/ requests and enforces per-user rate limits on counter operations.
  • Instrument ActionService.counter() with audit logging that records the caller, target id, modified field, and delta value for later review.

Monitoring Recommendations

  • Monitor the FlyCms audit trail for high-frequency counter calls or large negative deltas against stock and price fields.
  • Alert on sequential id enumeration patterns against the counter endpoints from any single session.
  • Review database triggers or change data capture streams for updates to monetary and inventory fields that lack a matching ownership context.

How to Mitigate CVE-2026-112294

Immediate Actions Required

  • Restrict access to /ucenter/action/{modelCode}/{id}/counter and /ucenter/action/compose at the reverse proxy until a patched build is deployed.
  • Audit recent counter activity in the database and roll back unauthorized changes to price, stock, and points fields.
  • Rotate or disable accounts that show evidence of enumerating or targeting rows owned by other users.

Patch Information

No upstream patch was referenced in the NVD entry at publication. Operators should track the upstream repository through GitHub Issue #19 and apply a fix that updates checkRowOwner in ActionService.java to compare the row's owner identifier against the authenticated session user before mutating the record.

Workarounds

  • Add a server-side ownership check in ActionController that rejects requests when the target row's owner column does not equal the current user identifier.
  • Disable the counter functionality for untrusted user tiers by blocking the affected routes at the application gateway.
  • Constrain mutable fields to a strict allowlist and reject counter requests that reference price, stock, or points unless invoked by an administrator role.
bash
# Example reverse proxy rule to block the vulnerable endpoints until patched
location ~ ^/ucenter/action/(.+/counter|compose)$ {
    return 403;
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.