/

CVE-2026-52021

Severity:

HIGH RISK

(7.5)

Information Disclosure (CWE-200) in 100xdevs CMS App

CVE-2026-52021

Deferred

Vulnerability type

Category:

Information Disclosure

CWE:

CWE-200

Impact:

Sensitive Information Exposure

Severity:

HIGH RISK

(7.5)

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 information disclosure vulnerability in 100xdevs CMS v1.0 may allow a remote attacker to obtain sensitive information through the middleware and mobile search API components.

The issue becomes risky when these request paths expose data without sufficiently restricting access, filtering responses, or protecting sensitive backend details.

Affected context

The vulnerability affects deployments of code100xDevs 100xdevs CMS v1.0 where remote requests reach src/middleware.ts or src/app/api/mobile/search/route.ts. The available information and exposure conditions may depend on application configuration, authorization behavior, response filtering, and the sensitivity of data handled by these components.

Exploit preconditions

  • Attack surface: Network-accessible CMS middleware and mobile search API
  • Required access: Ability to send requests to the affected application endpoints; authentication requirements may vary by deployment
  • Trigger point: Request processing through the middleware or mobile search route
  • Why exploitation is possible: Insufficient access control, response filtering, or data-handling boundaries may allow sensitive information to be returned to an unauthorized remote requester

Why this happens

The underlying issue is an information disclosure condition mapped to CWE-200. This class of weakness occurs when an application exposes sensitive data through a response, error path, middleware behavior, or API endpoint without adequately confirming that the requester is authorized to receive it. In this case, the affected middleware and mobile search components may process or return information beyond the intended trust boundary.

Potential impact

  • An attacker may obtain sensitive application or business information
  • Exposed data could support further targeted attacks
  • Users, administrators, or internal resources may be identified
  • Confidentiality of CMS-managed content or backend details could be reduced
  • Disclosed information could contribute to account compromise or unauthorized access when combined with other weaknesses

General mitigation guidance

Mitigation generally focuses on reducing the amount of information returned to remote clients and enforcing authorization at every sensitive request boundary.

Common defensive patterns include:

  • Applying explicit authentication and authorization checks to middleware and API routes
  • Returning only the minimum fields required by each client
  • Enforcing server-side filtering rather than relying on client-side restrictions
  • Avoiding sensitive values in errors, metadata, debug output, and search responses
  • Using secure-by-default route policies and deny-by-default access controls
  • Separating public search data from protected administrative or internal records
  • Running the application with least-privilege access to backing services and data stores

How teams detect issues like this

Organizations can assess this class of issue through:

  • Static analysis and code review for missing authorization checks in middleware and API handlers
  • Review of response serialization and search-field selection for excessive data exposure
  • Testing authenticated and unauthenticated requests across role boundaries
  • API policy checks that flag sensitive fields in publicly reachable responses
  • Monitoring access logs for unusual enumeration, repeated search requests, or requests to protected routes
  • Automated security testing that compares responses across identities with different privileges

Sources

SourceLink
gist.github.comgist.github.com/itsmohitnarayan/e456399f083130962bab6c710f208437
github.comgithub.com/code100x/cms

Frequently asked

questions

Yes. The affected components are reachable through the application, so a remote attacker may exploit the issue by sending requests when deployment controls permit access to the relevant routes.

Not necessarily. The required access depends on the application's middleware and endpoint authorization configuration; improperly protected routes may be accessible without authentication.

Enforce authorization before processing sensitive requests, return only necessary data, and apply server-side filtering to every response.

Use deny-by-default route policies, review API response schemas, test access across roles, avoid detailed error output, and monitor for data-enumeration behavior.

Find out what's already
exploitable in your codebase.