Summary
Feehi CMS up to version 2.1.1 exposes the /api/articles REST endpoint without proper authentication controls, allowing unauthenticated remote access.
Under typical deployments, this can let attackers read or manipulate article-related data over the network whenever the API is reachable from untrusted environments.
Affected context
This vulnerability arises in Feehi CMS installations that expose the /api/articles REST API endpoint to users or systems without enforcing strong authentication checks.
It is most relevant when the CMS is reachable from the public internet or untrusted internal networks, and when article data is considered sensitive or controls publishing workflows.
Exploit preconditions
- Attack surface: Network-exposed
/api/articlesREST API endpoint on the Feehi CMS server. - Required access: Remote network access to the CMS instance; no valid user credentials are needed if the endpoint is left unauthenticated.
- Trigger point: Direct HTTP requests to the vulnerable REST path using crafted parameters that rely on missing or ineffective authentication logic.
- Why exploitation is possible: The handler for the
/api/articlesroute does not consistently validate caller identity or enforce session/auth tokens, leading to CWE-287 (Improper Authentication) and CWE-306 (Missing Authentication for Critical Functionality).
Why this happens
The core issue stems from business logic that assumes the /api/articles endpoint can be safely accessed without robust authentication or authorization checks.
Request handlers either skip verifying user identity or rely on incomplete indicators (such as optional tokens) before performing operations on article resources.
This pattern maps to CWE-287 and CWE-306: critical functionality is exposed without mandatory authentication, allowing unauthenticated clients to invoke operations that should be restricted.
Potential impact
- Unauthenticated users may read article metadata or content that should be limited to specific roles.
- Attackers could modify, create, or delete articles if the endpoint supports write operations.
- Publication workflows and editorial integrity can be compromised through unauthorized content changes.
- The CMS instance may be used as a platform for disinformation, spam, or SEO abuse by altering visible content.
General mitigation guidance
Effective mitigation focuses on enforcing strong, consistent authentication and authorization for all REST endpoints that interact with content or configuration.
Common patterns include:
- Requiring authenticated sessions or tokens for every state-changing or data-retrieval operation on
/api/articles. - Centralizing access control checks so that API handlers cannot bypass authentication logic.
- Applying role-based permissions to ensure only appropriate identities can manage or publish articles.
- Designing the API to be secure-by-default, treating unauthenticated requests as denied unless explicitly allowed for non-sensitive, read-only data.
How teams detect issues like this
Detection typically involves reviewing REST controller code and routing configurations to confirm that each endpoint enforces authentication middleware or equivalent checks.
Static analysis and automated code review can flag handlers that:
- Lack authentication decorators or filters.
- Access data stores directly without prior identity verification.
- Perform create, update, or delete operations based solely on request parameters.
Security policies can require that any new REST endpoint be covered by authentication and authorization tests in CI, and periodic runtime scans can attempt unauthenticated access to APIs to detect exposed paths.

