CVE-2026-13544
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA flaw has been found in Feehi CMS up to 2.1.1. Affected by this issue is some unknown functionality of the file /api/users of the component API. This manipulation causes improper access controls. The attack can be initiated remotely. The exploit has been published and may be used. The project was informed of the problem early through an issue report but has not responded yet.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceFeehi CMS up to version 2.1.1 has improper access controls on the /api/users API endpoint, allowing remote attackers to access or manipulate user data without proper authorization. The vulnerability affects the API component's user-related functionality.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Feehi CMS installationLocate Feehi CMS on the system by checking web server document roots for common Feehi CMS file structures (e.g., index.php, common/config/main.php, or similar CMS directory structures)Affected if Feehi CMS is present on the server
-
Determine installed versionCheck the version file or admin panel for the Feehi CMS version number. Look for version.php, composer.json, or the admin dashboard version displayAffected if Version is 2.1.1 or lower
-
Verify API endpoint existsConfirm the /api/users endpoint is accessible by reviewing application routing configuration (e.g., api/config/main.php or equivalent routing files) and testing the endpoint with a web requestAffected if The /api/users endpoint is registered and accessible in the application
-
Test endpoint access controlSend an HTTP request to /api/users (GET for listing users, or POST for creating users) without providing authentication credentials or using an unauthenticated sessionAffected if The endpoint returns user data or allows operations without requiring valid authentication or authorization
-
Check API authentication configurationInspect the API component's authentication middleware or controller code (typically in api/controllers or api/modules) to determine if user authorization is enforced before processing requests to /api/usersAffected if No authentication check is found or authentication is improperly implemented for this endpoint
A system is affected if Feehi CMS version 2.1.1 or lower is installed and the /api/users endpoint can be accessed or manipulated without proper authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUntil a vendor patch is released, restrict network access to the /api/users endpoint (e.g., via firewall or WAF rules) and implement role-based access control (RBAC) at the application level. Consider disabling the API if not needed.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13544 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-13544 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data