CVE-2026-134675 — Beromir Servas (1.2.0) — CWE-639
CVE-2026-134675 is a HIGH severity Missing Authorization & Access Control vulnerability (CWE-639) (CVSS 7.1/10) affecting Beromir Servas (1.2.0). Technical vector analysis shows that an attacker can exploit this flaw remotely over the network with low-privileged access (PR:L) with zero user interaction (UI:N), posing a direct security risk to affected deployments.
📄 Official NVD / MITRE Original Record Text
Servas before 1.2.0 contains a missing authorization vulnerability that allows authenticated users to modify and delete other users' data by supplying target resource ids. Attackers can abuse TagController update and destroy, LinkController destroy, and GroupController destroy actions to rename or delete tags and delete links and groups.
🎯 What is this vulnerability?
CVE‑2026‑134675 is a classic authorization bypass flaw (CWE‑639) in Servas 1.2.0.
The application’s TagController, LinkController, and GroupController lack a proper ownership check when processing update and destroy actions. An authenticated user can supply any resource identifier (e.g., a tag ID, link ID, or group ID) and the request will be executed as if the user owned that resource.
Key points:
| Attribute | Detail |
|---|---|
| Missing check | The controllers do not verify that the authenticated user is the owner or has the required role before performing the action. |
| Affected actions | TagController.update, TagController.destroy, LinkController.destroy, GroupController.destroy. |
| Impact | An attacker can rename, delete, or otherwise modify *any* user’s tags, links, or groups. |
| CWE | 639 – Authorization Bypass Through User‑Controlled Key |
| CVSS | 7.1 (High) – Confidentiality impact is “High” because data can be deleted or altered; Integrity is also “High”; Availability is “None”. |
The flaw does not allow arbitrary code execution, privilege escalation to a higher role, or unauthenticated access. It only permits an authenticated user with low privileges to affect other users’ data.
⚡ Attack Chain
NOTE: The exact URI paths and parameter names are not specified in the CVE description. The following examples use the most common RESTful patterns that are illustrative of the vulnerability class.
1. Discovery & Reconnaissance
| Step | Technique | What to look for |
|---|---|---|
| Version fingerprinting | HTTP header inspection, /api/v1/version, or /admin login page | Look for “Servas 1.2.0” or a version string in the response. |
| Endpoint enumeration | Automated scanning (e.g., DirBuster, Burp Suite Intruder) | Discover endpoints such as /api/v1/tags, /api/v1/links, /api/v1/groups. |
| User enumeration | Enumerate user IDs via /api/v1/users or by observing X-User-ID headers | Identify numeric or UUID IDs that can be used as target resource identifiers. |
2. Exploitation
Assume the attacker is logged in as user alice (user ID 42). The attacker wants to delete a tag owned by user bob (tag ID 9876).
# 1. Obtain a valid session cookie or bearer token (already authenticated as alice)
# Example: cookie "session_id=abc123"
# 2. Delete Bob's tag (illustrative endpoint)
curl -X DELETE \
-H "Cookie: session_id=abc123" \
-H "Content-Type: application/json" \
"https://target.example.com/api/v1/tags/9876"
# 3. Rename Bob's link (illustrative endpoint)
curl -X PUT \
-H "Cookie: session_id=abc123" \
-H "Content-Type: application/json" \
-d '{"name":"New Link Name"}' \
"https://target.example.com/api/v1/links/5432"
# 4. Delete Bob's group (illustrative endpoint)
curl -X DELETE \
-H "Cookie: session_id=abc123" \
-H "Content-Type: application/json" \
"https://target.example.com/api/v1/groups/1122"What the request does:
1. The DELETE /api/v1/tags/9876 request is processed by TagController.destroy.
2. The controller fetches the tag by ID 9876 but does not check that tag.owner_id == current_user.id.
3. The tag is deleted regardless of ownership.
4. Similar logic applies to LinkController.destroy and GroupController.destroy.
5. TagController.update allows renaming or modifying tag attributes without an ownership check.
Important: If the actual API uses different paths (e.g.,/tags/:idor/tags?id=9876), the same principle applies: the controller must enforce an ownership or role check before performing the action.
3. Post‑Exploitation
| Goal | How it’s achieved |
|---|---|
| Data loss | Delete tags, links, or groups belonging to other users, effectively removing their data from the system. |
| Data integrity | Rename or modify tags/links/groups, corrupting the logical structure of the user’s data. |
| Disruption | Removing groups can break access control or collaboration features, causing service disruption for other users. |
| Further exploitation | While the flaw itself does not grant higher privileges, the attacker can use the deleted or renamed data to confuse users, create a denial‑of‑service scenario, or facilitate social‑engineering attacks by manipulating the data structure. |
🌍 Real World Impact
| Impact | CVSS Vector | Explanation |
|---|---|---|
| Confidentiality | VI:H | Deleting or renaming data can expose sensitive information if the attacker later reads the remaining data or if the system logs the deletion. |
| Integrity | VI:H | Unauthorized modifications corrupt user data, leading to loss of trust and potential legal ramifications. |
| Availability | VA:N | The flaw does not directly cause downtime; however, mass deletions could degrade performance or trigger backups, indirectly affecting availability. |
| Scope | SI:N | The vulnerability does not affect other components or services outside Servas. |
| Privileges | PR:L | Only authenticated users with low privileges are required. |
Practical consequences:
- Data loss: Users lose tags, links, or groups, which may contain critical business information.
- Operational disruption: Collaboration features break if groups are deleted.
- Audit trail corruption: Renamed tags can mislead forensic investigations.
- Reputational damage: Clients may lose confidence in the platform’s data integrity.
🛡️ Remediation & Mitigation
1. Patch
| Affected version | Fixed version | Upgrade recommendation |
|---|---|---|
| Servas < 1.2.0 | 1.2.0 or later | Apply the official patch or upgrade to the latest stable release (≥ 1.2.0). |
NOTE: The CVE description states “before 1.2.0” is vulnerable. Therefore, any release 1.2.0 or newer is considered safe.
2. Workarounds (if patching is not immediately possible)
| Mitigation | Implementation | |
|---|---|---|
| Restrict controller access | Configure the web framework’s routing or middleware to allow TagController, LinkController, and GroupController actions only for users with the admin role. Example (pseudo‑Ruby on Rails):<br>before_action :require_admin, only: [:update, :destroy] | |
| WAF / ModSecurity rule | Block requests that attempt to modify resources owned by other users. Example rule (illustrative):<br>SecRule REQUEST_URI "@beginsWith /api/v1/tags" "phase:2,chain,log,deny,status:403,rev:'1.0',msg:'Unauthorized tag modification'"<br>SecRule REQUEST_METHOD "^(PUT | DELETE)$" "chain"<br>SecRule REQUEST_HEADERS:Cookie "@rx session_id=[^;]+"<br>SecRule REQUEST_HEADERS:Cookie "@rx user_id=([0-9]+)"<br>SecRule REQUEST_HEADERS:Cookie "@rx user_id=([0-9]+)" "t:none,rev:'1.0',msg:'Tag ownership mismatch',id:1001,phase:2,log,deny,status:403" |
| Disable vulnerable endpoints | If tags/links/groups are not critical, temporarily disable the destroy and update actions via configuration or by commenting out the routes. | |
| Audit logs | Enable detailed logging of PUT/DELETE requests to the affected controllers, including the authenticated user ID and target resource ID. |
3. Detection
| Indicator | Log pattern | IoC |
|---|---|---|
| Unauthorized delete | DELETE /api/v1/tags/9876 | HTTP 200/204 returned for a user who is not the owner |
| Unauthorized update | PUT /api/v1/links/5432 | HTTP 200/204 returned with name= field changed |
| Multiple deletions | > 10 DELETE requests in 5 min | Burst of 200/204 responses from /api/v1/groups |
| Suspicious user activity | User ID 42 performing actions on resource IDs belonging to other users | user_id=42 in session cookie + resource_id=9876 in request |
Sample log entry (Apache/Nginx combined log format):
192.0.2.10 - alice [22/Nov/2026:14:32:07 +0000] "DELETE /api/v1/tags/9876 HTTP/1.1" 200 123 "-" "Mozilla/5.0"If the user_id in the session does not match the owner of tag 9876, flag the event.
⚠️ Urgency
Bottom line: CVE‑2026‑134675 is a classic missing‑authorization flaw that allows any authenticated user to delete or rename other users’ tags, links, and groups. The impact is high on confidentiality and integrity, with no direct availability effect. The fix is a simple upgrade to Servas 1.2.0 or later; until then, restrict access to the vulnerable controllers or block the offending requests with a WAF.
[🤖 CVE Professor AI Security Engine]
FOFA Query