Vulnerability-Lookup

CNVD-2026-18148

Vulnerability from cnvd - Published: 2026-04-22

Title

StudioCMS信息泄露漏洞

Description

StudioCMS是StudioCMS开源的一个内容管理系统。 StudioCMS存在信息泄露漏洞，该漏洞源于REST API getUsers端点使用攻击者控制的rank查询参数，攻击者可利用该漏洞导致管理员令牌获取所有者账户记录，造成授权不一致。

Severity

低

Patch Name

StudioCMS信息泄露漏洞的补丁

Patch Description

StudioCMS是StudioCMS开源的一个内容管理系统。 StudioCMS存在信息泄露漏洞，该漏洞源于REST API getUsers端点使用攻击者控制的rank查询参数，攻击者可利用该漏洞导致管理员令牌获取所有者账户记录，造成授权不一致。目前，供应商发布了安全公告及相关补丁信息，修复了此漏洞。

Formal description

目前厂商已发布升级补丁以修复漏洞，补丁获取链接： https://studiocms.dev/

Reference

https://nvd.nist.gov/vuln/detail/CVE-2026-32638

Impacted products

Name
StudioCMS StudioCMS <0.4.4

Show details on source website

JSON

To clipboard

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2026-32638",
      "cveUrl": "https://nvd.nist.gov/vuln/detail/CVE-2026-32638"
    }
  },
  "description": "StudioCMS\u662fStudioCMS\u5f00\u6e90\u7684\u4e00\u4e2a\u5185\u5bb9\u7ba1\u7406\u7cfb\u7edf\u3002\n\nStudioCMS\u5b58\u5728\u4fe1\u606f\u6cc4\u9732\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8eREST API getUsers\u7aef\u70b9\u4f7f\u7528\u653b\u51fb\u8005\u63a7\u5236\u7684rank\u67e5\u8be2\u53c2\u6570\uff0c\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u5bfc\u81f4\u7ba1\u7406\u5458\u4ee4\u724c\u83b7\u53d6\u6240\u6709\u8005\u8d26\u6237\u8bb0\u5f55\uff0c\u9020\u6210\u6388\u6743\u4e0d\u4e00\u81f4\u3002",
  "formalWay": "\u76ee\u524d\u5382\u5546\u5df2\u53d1\u5e03\u5347\u7ea7\u8865\u4e01\u4ee5\u4fee\u590d\u6f0f\u6d1e\uff0c\u8865\u4e01\u83b7\u53d6\u94fe\u63a5\uff1a\r\nhttps://studiocms.dev/",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2026-18148",
  "openTime": "2026-04-22",
  "patchDescription": "StudioCMS\u662fStudioCMS\u5f00\u6e90\u7684\u4e00\u4e2a\u5185\u5bb9\u7ba1\u7406\u7cfb\u7edf\u3002\r\n\r\nStudioCMS\u5b58\u5728\u4fe1\u606f\u6cc4\u9732\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8eREST API getUsers\u7aef\u70b9\u4f7f\u7528\u653b\u51fb\u8005\u63a7\u5236\u7684rank\u67e5\u8be2\u53c2\u6570\uff0c\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u5bfc\u81f4\u7ba1\u7406\u5458\u4ee4\u724c\u83b7\u53d6\u6240\u6709\u8005\u8d26\u6237\u8bb0\u5f55\uff0c\u9020\u6210\u6388\u6743\u4e0d\u4e00\u81f4\u3002\u76ee\u524d\uff0c\u4f9b\u5e94\u5546\u53d1\u5e03\u4e86\u5b89\u5168\u516c\u544a\u53ca\u76f8\u5173\u8865\u4e01\u4fe1\u606f\uff0c\u4fee\u590d\u4e86\u6b64\u6f0f\u6d1e\u3002",
  "patchName": "StudioCMS\u4fe1\u606f\u6cc4\u9732\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": "StudioCMS StudioCMS \u003c0.4.4"
  },
  "referenceLink": "https://nvd.nist.gov/vuln/detail/CVE-2026-32638",
  "serverity": "\u4f4e",
  "submitTime": "2026-03-20",
  "title": "StudioCMS\u4fe1\u606f\u6cc4\u9732\u6f0f\u6d1e"
}

CVE-2026-32638 (GCVE-0-2026-32638)

Vulnerability from cvelistv5 – Published: 2026-03-18 20:41 – Updated: 2026-03-19 15:01

Title

StudioCMS REST getUsers Exposes Owner Account Records to Admin Tokens

Summary

StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.4, the REST API `getUsers` endpoint in StudioCMS uses the attacker-controlled `rank` query parameter to decide whether owner accounts should be filtered from the result set. As a result, an admin token can request `rank=owner` and receive owner account records, including IDs, usernames, display names, and email addresses, even though the adjacent `getUser` endpoint correctly blocks admins from viewing owner users. This is an authorization inconsistency inside the same user-management surface. Version 0.4.4 fixes the issue.

Severity

2.7 (Low)


                        
                          CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N

SSVC

Exploitation: poc Automatable: no Technical Impact: partial

CISA Coordinator · CISA-ADP (v2.0.3)

Decision recorded 2026-03-19 15:00 UTC

CWE

CWE-639 - Authorization Bypass Through User-Controlled Key

Assigner

GitHub_M mitre root

References

3 references

URL	Tags
https://github.com/withstudiocms/studiocms/securi…	x_refsource_CONFIRM
https://github.com/withstudiocms/studiocms/commit…	x_refsource_MISC
https://github.com/withstudiocms/studiocms/releas…	x_refsource_MISC

Impacted products

1 product

Vendor	Product	Version
withstudiocms	studiocms	Affected: < 0.4.4

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-32638",
                "options": [
                  {
                    "Exploitation": "poc"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-03-19T15:00:04.391194Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-03-19T15:01:00.396Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "studiocms",
          "vendor": "withstudiocms",
          "versions": [
            {
              "status": "affected",
              "version": "\u003c 0.4.4"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.4, the REST API `getUsers` endpoint in StudioCMS uses the attacker-controlled `rank` query parameter to decide whether owner accounts should be filtered from the result set. As a result, an admin token can request `rank=owner` and receive owner account records, including IDs, usernames, display names, and email addresses, even though the adjacent `getUser` endpoint correctly blocks admins from viewing owner users. This is an authorization inconsistency inside the same user-management surface. Version 0.4.4 fixes the issue."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 2.7,
            "baseSeverity": "LOW",
            "confidentialityImpact": "LOW",
            "integrityImpact": "NONE",
            "privilegesRequired": "HIGH",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N",
            "version": "3.1"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-639",
              "description": "CWE-639: Authorization Bypass Through User-Controlled Key",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-03-18T20:41:14.034Z",
        "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "shortName": "GitHub_M"
      },
      "references": [
        {
          "name": "https://github.com/withstudiocms/studiocms/security/advisories/GHSA-xvf4-ch4q-2m24",
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://github.com/withstudiocms/studiocms/security/advisories/GHSA-xvf4-ch4q-2m24"
        },
        {
          "name": "https://github.com/withstudiocms/studiocms/commit/aebe8bcb3618bb07c6753e3f5c982c1fe6adea64",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/withstudiocms/studiocms/commit/aebe8bcb3618bb07c6753e3f5c982c1fe6adea64"
        },
        {
          "name": "https://github.com/withstudiocms/studiocms/releases/tag/studiocms@0.4.4",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/withstudiocms/studiocms/releases/tag/studiocms@0.4.4"
        }
      ],
      "source": {
        "advisory": "GHSA-xvf4-ch4q-2m24",
        "discovery": "UNKNOWN"
      },
      "title": "StudioCMS REST getUsers Exposes Owner Account Records to Admin Tokens"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
    "assignerShortName": "GitHub_M",
    "cveId": "CVE-2026-32638",
    "datePublished": "2026-03-18T20:41:14.034Z",
    "dateReserved": "2026-03-12T15:29:36.560Z",
    "dateUpdated": "2026-03-19T15:01:00.396Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted

CNVD-2026-18148

CVE-2026-32638 (GCVE-0-2026-32638)

Tags

Sightings

Nomenclature

Related by attack behaviour