Publish Advisories

GHSA-6w82-v552-wjw2
GHSA-f4cf-9rvr-2rcx
GHSA-wqv2-4wpg-8hc9
GHSA-x93p-w2ch-fg67
GHSA-rpr2-4hqj-hc4q

Author: advisory-database[bot]

advisories/github-reviewed/2025/12/GHSA-6w82-v552-wjw2/GHSA-6w82-v552-wjw2.json

@@ -1,9 +1,11 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-6w82-v552-wjw2",
-  "modified": "2025-12-09T17:24:21Z",
+  "modified": "2025-12-10T20:02:23Z",
   "published": "2025-12-09T17:24:21Z",
-  "aliases": [],
+  "aliases": [
+    "CVE-2025-67648"
+  ],
   "summary": "Shopware Storefront Reflected XSS in Storefront Login Page",
   "details": "### Impact\n\nBy exploiting the XSS vulnerabilities, malicious actors can perform harmful actions in the user's web browser in the session context of the affected user. Some examples of this include, but are not limited to: Obtaining user session tokens. Performing administrative actions (when an administrative user is affected). These vulnerabilities pose a high security risk. Since a sensitive cookie is not configured with the HttpOnly attribute and administrator JWTs are stored in sessionStorage, any successful XSS attack could enable the theft of session cookies and administrative tokens.\n\n### Description\n\nA request parameter from the URL of the login page is directly rendered within the Twig template of the Storefront login page without further processing or input validation. This allows direct code injection into the template via the URL parameter. An attacker can create malicious links that could be used in a phishing attack. The parameter `waitTime` lacks proper input validation.\n\nThe attack can be tested with the following URL pattern:\n\n```\n/account/login?loginError=1&waitTime=<a%20href%3D\"https%3A%2F%2Fde.wikipedia.org%2Fwiki%2FPhishing\">Here<%2Fa>\n```\n\nThe same applies to the `errorSnippet` parameter:\n\n```\n/account/login?loginError=1&errorSnippet=Reset%20your%20password%20%3Ca%20href%3D%22https%3A%2F%2Fde.wikipedia.org%2Fwiki%2FPhishing%22%3Ehere%3C%2Fa%3E.\n```",
   "severity": [

advisories/github-reviewed/2025/12/GHSA-f4cf-9rvr-2rcx/GHSA-f4cf-9rvr-2rcx.json

@@ -1,9 +1,11 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-f4cf-9rvr-2rcx",
-  "modified": "2025-12-10T18:20:01Z",
+  "modified": "2025-12-10T20:02:40Z",
   "published": "2025-12-10T18:20:01Z",
-  "aliases": [],
+  "aliases": [
+    "CVE-2025-67717"
+  ],
   "summary": "Zitadel Discloses the Total Number of Instance Users",
   "details": "### Summary\n\nZitadel's User Service discloses the total number of instance users to unauthorized users.\n\n### Impact\n\nThe ZITADEL User Service exposes the total number of users within an instance to any authenticated user, regardless of their specific permissions. While this does not leak individual user data or PII, disclosing the total user count via the `totalResult` field constitutes an information disclosure vulnerability that may be sensitive in certain contexts.\n\n### Affected Versions\n\nSystems running one of the following version are affected:\n\n- **4.x**: `4.0.0-rc.1` through `4.7.1`\n- **3.x**: `3.0.0-rc.1` through `3.4.4`\n- **2.x**: `2.44.0` through `2.71.19`\n\n### Patches\n\nThe vulnerability has been addressed in the latest release. The patch resolves the issue and returns the `totalResult` value corresponding to the number of instance users for whom the querying user has read permission.\n\n- 4.x: Upgrade to >=[4.7.2](https://github.com/zitadel/zitadel/releases/tag/v4.7.2)\n- 3.x: Update to >=[3.4.5](https://github.com/zitadel/zitadel/releases/tag/v3.4.5)\n- 2.x: Update to >=[3.4.5](https://github.com/zitadel/zitadel/releases/tag/v3.4.5) (or checkout the workarounds section)\n\n### Workarounds\n\nThe recommended solution is to update Zitadel to a patched version.\n\nIf a version upgrade is not possible, you can enable the `permissionCheckV2` feature on your instance.\n\n### Questions\n\nIf you have any questions or comments about this advisory, please email us at [[email protected]](mailto:[email protected])\n\n### Credits\n\nThis vulnerability was found by [zentrust partners GmbH](https://zentrust.partners) during a scheduled penetration test. Thank you to the analysts Martin Tschirsich, Joud Zakharia, Christopher Baumann.\nThe full report will be made public after the complete review.",
   "severity": [

advisories/github-reviewed/2025/12/GHSA-wqv2-4wpg-8hc9/GHSA-wqv2-4wpg-8hc9.json

@@ -1,9 +1,11 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-wqv2-4wpg-8hc9",
-  "modified": "2025-12-10T17:18:37Z",
+  "modified": "2025-12-10T20:02:32Z",
   "published": "2025-12-10T17:18:37Z",
-  "aliases": [],
+  "aliases": [
+    "CVE-2025-67713"
+  ],
   "summary": "Miniflux has an Open Redirect via protocol-relative redirect_url",
   "details": "### Summary\n`redirect_url` is treated as safe when `url.Parse(...).IsAbs()` is false. Protocol-relative URLs like `//ikotaslabs.com` have an empty scheme and pass that check, allowing post-login redirects to attacker-controlled sites.\n\n### Details\n- `url.Parse(\"//ikotaslabs.com\")` => empty Scheme, Host=\"ikotaslabs.com\".\n- `IsAbs()` returns false for `//ikotaslabs.com`, so the code treats it as allowed.\n- Browser resolves `//ikotaslabs.com` to current-origin scheme (e.g. `https://ikotaslabs.com`), enabling phishing flows after login.\n\n### PoC\n1. Send or visit: `http://localhost/login?redirect_url=//ikotaslabs.com`  \n2. Complete normal login flow.  \n3. After login the app redirects to `https://ikotaslabs.com` (or `http://` depending on origin).\n\n### Acknowledgements  \nThis vulnerability was discovered using the automated vulnerability analysis tools **VulScribe** and **PwnML**.  \nThe research and tool development were conducted with support from the **MITOU Advanced Program (未踏アドバンスト事業)**,  \nadministered by the **Information-technology Promotion Agency (IPA), Japan**.",
   "severity": [

advisories/github-reviewed/2025/12/GHSA-x93p-w2ch-fg67/GHSA-x93p-w2ch-fg67.json

@@ -1,9 +1,11 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-x93p-w2ch-fg67",
-  "modified": "2025-12-10T18:20:55Z",
+  "modified": "2025-12-10T20:02:47Z",
   "published": "2025-12-10T18:20:55Z",
-  "aliases": [],
+  "aliases": [
+    "CVE-2025-67719"
+  ],
   "summary": "Ibexa User Bundle is missing password change validation",
   "details": "### Impact\nThe vulnerability is in the password change dialog in the back office. During the transition from v4 to v5 a mistake was made in the validation code which caused the validation of the previous password to not run as expected. This made it possible for a logged in user to change password in the back office without knowing the previous password. For example if someone logs in, leaves their workstation unlocked, and another person uses the same machine.\n\n### Credit\nThe issue was reported to us by Code-Rhapsodie. We thank them for their responsible disclosure!\nhttps://www.code-rhapsodie.fr/\n\n### Patches\n- See \"Patched versions\".\n- https://github.com/ibexa/user/commit/9d485bf385e6401c9f7ee80287d8ccd00f73dcf4\n\n### Workarounds\nNone.",
   "severity": [