CVE Professor
›
Back
CVE-2026-134675

CVE-2026-134675 — Beromir Servas (1.2.0) — CWE-639

HIGH CVSS 7.1 CIRCL

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.

Published 22.11.2026
ISO Date 2026-11-22
CVSS Version v4.0
Source CIRCL
CVSS v4.0 Vector Metrics
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
Attack Vector Network AV:N
Attack Complexity Low AC:L
Attack Reqs. None AT:N
Privileges Req. Low PR:L
User Interaction None UI:N
Vuln. Conf. None VC:N
Vuln. Integrity High VI:H
Vuln. Avail. None VA:N
Subseq. Conf. None SC:N
Subseq. Integ. None SI:N
Subseq. Avail. None SA:N
AI Security Analysis & Remediation

🎯 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:

AttributeDetail
Missing checkThe controllers do not verify that the authenticated user is the owner or has the required role before performing the action.
Affected actionsTagController.update, TagController.destroy, LinkController.destroy, GroupController.destroy.
ImpactAn attacker can rename, delete, or otherwise modify *any* user’s tags, links, or groups.
CWE639 – Authorization Bypass Through User‑Controlled Key
CVSS7.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

StepTechniqueWhat to look for
Version fingerprintingHTTP header inspection, /api/v1/version, or /admin login pageLook for “Servas 1.2.0” or a version string in the response.
Endpoint enumerationAutomated scanning (e.g., DirBuster, Burp Suite Intruder)Discover endpoints such as /api/v1/tags, /api/v1/links, /api/v1/groups.
User enumerationEnumerate user IDs via /api/v1/users or by observing X-User-ID headersIdentify 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/:id or /tags?id=9876), the same principle applies: the controller must enforce an ownership or role check before performing the action.

3. Post‑Exploitation

GoalHow it’s achieved
Data lossDelete tags, links, or groups belonging to other users, effectively removing their data from the system.
Data integrityRename or modify tags/links/groups, corrupting the logical structure of the user’s data.
DisruptionRemoving groups can break access control or collaboration features, causing service disruption for other users.
Further exploitationWhile 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

ImpactCVSS VectorExplanation
ConfidentialityVI:HDeleting or renaming data can expose sensitive information if the attacker later reads the remaining data or if the system logs the deletion.
IntegrityVI:HUnauthorized modifications corrupt user data, leading to loss of trust and potential legal ramifications.
AvailabilityVA:NThe flaw does not directly cause downtime; however, mass deletions could degrade performance or trigger backups, indirectly affecting availability.
ScopeSI:NThe vulnerability does not affect other components or services outside Servas.
PrivilegesPR:LOnly 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 versionFixed versionUpgrade recommendation
    Servas < 1.2.01.2.0 or laterApply 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)

    MitigationImplementation
    Restrict controller accessConfigure 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 ruleBlock 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 "^(PUTDELETE)$" "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 endpointsIf tags/links/groups are not critical, temporarily disable the destroy and update actions via configuration or by commenting out the routes.
    Audit logsEnable detailed logging of PUT/DELETE requests to the affected controllers, including the authenticated user ID and target resource ID.

    3. Detection

    IndicatorLog patternIoC
    Unauthorized deleteDELETE /api/v1/tags/9876HTTP 200/204 returned for a user who is not the owner
    Unauthorized updatePUT /api/v1/links/5432HTTP 200/204 returned with name= field changed
    Multiple deletions> 10 DELETE requests in 5 minBurst of 200/204 responses from /api/v1/groups
    Suspicious user activityUser ID 42 performing actions on resource IDs belonging to other usersuser_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

  • CVSS score: 7.1 (High) – indicates significant risk if exploited.
  • Exploit complexity: Low (authenticated, no special privileges).
  • CISA KEV status: No – no known widespread exploitation, but the flaw is still exploitable.
  • Recommended priority: Immediate.
- Patch: Upgrade to Servas 1.2.0 or later as soon as possible. - If patching is delayed: Apply the workarounds above and monitor logs for suspicious activity. - Post‑patch: Verify that ownership checks are enforced by attempting a test delete with a non‑owner user and ensuring the request is denied.
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]

Target Reconnaissance Queries (FOFA & Shodan)

FOFA Query

app="beromir Servas"
CVSS Score
7.1 / 10 · CVSS HIGH
Weakness Types (CWE)
CWE-639
Affected Products (1)
beromir:Servas (1.2.0)
Related CVEs
7.1
CVE-2026-134678
Freedit before 0.9.9 contains an authorization bypass vulnerability in the edit_post_post handler for POST /po
5.4
CVE-2026-134674
Freedit before 0.9.9 contains an authorization bypass vulnerability in the post_lock, post_hide, post_pin and
7.1
CVE-2026-134261
Admidio before 5.0.18 contains an insecure direct object reference vulnerability in mylist.php that loads list
6.5
CVE-2026-134371
Frappe 8.8.0 before 16.30.0 contains an insecure direct object reference vulnerability in the SMS Settings get
5.9
CVE-2026-134317
@better-auth/stripe 1.2.0-beta.18 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contains an authorization
5.4
CVE-2026-134356
AzuraCast 0.19.0 before 0.24.1 contains an improper authorization vulnerability that allows users with station