GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration
Common Weakness Enumeration

CWE-613

Allowed-with-Review

Insufficient Session Expiration

Abstraction: Base · Status: Incomplete

API response cwe.mitre.org

According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization."

974 vulnerabilities reference this CWE, most recent first.

GHSA-H533-Q6JC-QX28

Vulnerability from github – Published: 2022-05-13 01:07 – Updated: 2024-02-28 21:02
VLAI
Summary
Cloud Foundry Runtime Insufficient Session Expiration vulnerability
Details

The password change functionality in Cloud Foundry Runtime cf-release before 216, UAA before 2.5.2, and Pivotal Cloud Foundry (PCF) Elastic Runtime before 1.7.0 allow attackers to have unspecified impact by leveraging failure to expire existing sessions.

Severity
9.8 (Critical)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Maven",
        "name": "org.cloudfoundry.identity:cloudfoundry-identity-server"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.5.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2015-5171"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-613"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2024-02-28T21:02:57Z",
    "nvd_published_at": "2017-10-24T17:29:00Z",
    "severity": "CRITICAL"
  },
  "details": "The password change functionality in Cloud Foundry Runtime cf-release before 216, UAA before 2.5.2, and Pivotal Cloud Foundry (PCF) Elastic Runtime before 1.7.0 allow attackers to have unspecified impact by leveraging failure to expire existing sessions.",
  "id": "GHSA-h533-q6jc-qx28",
  "modified": "2024-02-28T21:02:57Z",
  "published": "2022-05-13T01:07:00Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2015-5171"
    },
    {
      "type": "WEB",
      "url": "https://github.com/cloudfoundry/uaa/commit/7c70a85f4c7b5a9b1603bc57cab14a7ffef2168b"
    },
    {
      "type": "WEB",
      "url": "https://github.com/cloudfoundry/uaa/commit/9730cd6a3bbb481ee4e400b51952b537589c469d"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/cloudfoundry/uaa"
    },
    {
      "type": "WEB",
      "url": "https://pivotal.io/security/cve-2015-5170-5173"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Cloud Foundry Runtime Insufficient Session Expiration vulnerability"
}

GHSA-H57H-82MJ-62H6

Vulnerability from github – Published: 2026-05-12 21:31 – Updated: 2026-05-12 21:31
VLAI
Details

A session management vulnerability in AOS-8 allows previously authenticated users to retain network access after their accounts are administratively disabled. Existing sessions are not invalidated when credentials are revoked, enabling continued access until session expiration. An attacker with compromised credentials could exploit this behavior to maintain unauthorized access even after the account has been disabled.

Severity
5.4 (Medium)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2026-44873"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-613"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-05-12T20:16:45Z",
    "severity": "MODERATE"
  },
  "details": "A session management vulnerability in AOS-8 allows previously authenticated users to retain network access after their accounts are administratively disabled. Existing sessions are not invalidated when credentials are revoked, enabling continued access until session expiration. An attacker with compromised credentials could exploit this behavior to maintain unauthorized access even after the account has been disabled.",
  "id": "GHSA-h57h-82mj-62h6",
  "modified": "2026-05-12T21:31:35Z",
  "published": "2026-05-12T21:31:35Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-44873"
    },
    {
      "type": "WEB",
      "url": "https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbnw05048en_us\u0026docLocale=en_US"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-H5J9-CVRW-V5QH

Vulnerability from github – Published: 2026-04-01 23:48 – Updated: 2026-04-06 17:25
VLAI
Summary
listmonk's active sessions remain valid after password reset and password change
Details

Summary

A session management vulnerability allows previously issued authenticated sessions to remain valid after sensitive account security changes, specifically password reset and password change. As a result, an attacker who has already obtained a valid session cookie can retain access to the account even after the victim changes or resets their password.

This weakens account recovery and session security guarantees. I reproduced the issue on listmonk v6.0.0.

Details

The application updates account credentials successfully, but existing active sessions are not revoked afterward.

This behavior was confirmed in two flows:

  1. Password reset flow
  2. A user resets their password through the forgot/reset flow.
  3. The old password becomes invalid.
  4. The new password works.

  5. However, a session cookie issued before the reset remains valid and continues to authenticate successfully.

  6. Authenticated password change flow

  7. The same user logs in from two separate sessions.
  8. Using session A, the password is changed through the authenticated profile endpoint.
  9. The old password becomes invalid.
  10. The new password works.
  11. However, session B, issued before the password change, remains valid and continues to authenticate successfully.

From the source review, the reset flow consumes the reset token, updates the password, and creates a fresh session, but there does not appear to be any revocation of older sessions. The same applies to the profile password change flow.

Relevant code areas observed during review: - cmd/auth.go — forgot/reset flow - cmd/users.go — authenticated profile update flow - internal/core/users.go — password update path

Additionally: - It was verified that reset links are single-use. - It was verified that password reset on a TOTP-enabled account still enforces TOTP on fresh login. - However, already-issued sessions still remain valid after reset.

PoC

Case 1: Password reset does not revoke existing session

  1. Create or use a normal user account.
  2. Log in as that user and save the authenticated session cookie.
  3. Trigger forgot-password for the account.
  4. Use the emailed reset link and set a new password.
  5. Verify:
  6. the old password no longer works
  7. the new password works
  8. Replay the old pre-reset session cookie against an authenticated endpoint such as /api/profile.

Example validation request:

GET /api/profile HTTP/1.1
Host: 127.0.0.1:9000
Cookie: session=<old_pre_reset_session>

Observed result:

Server returns HTTP/1.1 200 OK Response contains the authenticated user profile

Case 2: Password change does not revoke other active sessions

  1. Log in twice as the same user and save two authenticated session cookies:
  2. session A

  3. session B

  4. Using session A, change the password through the authenticated profile update endpoint.

  5. Verify:

  6. the old password no longer works

  7. the new password works

  8. Replay session B against an authenticated endpoint such as /api/profile.

Example password change request:

PUT /api/profile HTTP/1.1
Host: 127.0.0.1:9000
Cookie: session=<session_A>
Content-Type: application/json

{
  "name":"victim1",
  "email":"victim1@test.local",
  "password":"VictimChanged123"
}

Then validate session B:

GET /api/profile HTTP/1.1
Host: 127.0.0.1:9000
Cookie: session=<session_B>

Observed result: - Server returns HTTP/1.1 200 OK - Response contains the authenticated user profile

Impact

This issue allows persistence of unauthorized access after credential recovery actions.

If an attacker has already stolen a valid session cookie through any means (for example malware, browser compromise, XSS, shared machine access, proxy leakage, or other session theft), the victim cannot fully recover the account by changing or resetting the password alone. The attacker’s existing session remains valid.

This impacts account recovery expectations and session security for all authenticated users, including users with TOTP enabled.

Attachment

listmonk-session-report.zip

Severity
7.1 (High)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/knadh/listmonk"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "1.1.1-0.20241028090858-319053dd7a90"
            },
            {
              "fixed": "1.1.1-0.20260329113754-1b5e8d38c778"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-34828"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-613"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-04-01T23:48:43Z",
    "nvd_published_at": "2026-04-02T18:16:33Z",
    "severity": "HIGH"
  },
  "details": "### Summary\nA session management vulnerability allows previously issued authenticated sessions to remain valid after sensitive account security changes, specifically password reset and password change. As a result, an attacker who has already obtained a valid session cookie can retain access to the account even after the victim changes or resets their password.\n\nThis weakens account recovery and session security guarantees. I reproduced the issue on listmonk v6.0.0.\n\n### Details\nThe application updates account credentials successfully, but existing active sessions are not revoked afterward.\n\nThis behavior was confirmed in two flows:\n\n1. **Password reset flow**\n   - A user resets their password through the forgot/reset flow.\n   - The old password becomes invalid.\n   - The new password works.\n   - However, a session cookie issued **before** the reset remains valid and continues to authenticate successfully.\n\n2. **Authenticated password change flow**\n   - The same user logs in from two separate sessions.\n   - Using session A, the password is changed through the authenticated profile endpoint.\n   - The old password becomes invalid.\n   - The new password works.\n   - However, session B, issued before the password change, remains valid and continues to authenticate successfully.\n\nFrom the source review, the reset flow consumes the reset token, updates the password, and creates a fresh session, but there does not appear to be any revocation of older sessions. The same applies to the profile password change flow.\n\nRelevant code areas observed during review:\n- `cmd/auth.go` \u2014 forgot/reset flow\n- `cmd/users.go` \u2014 authenticated profile update flow\n- `internal/core/users.go` \u2014 password update path\n\nAdditionally:\n- It was verified that reset links are single-use.\n- It was verified that password reset on a TOTP-enabled account still enforces TOTP on fresh login.\n- However, already-issued sessions still remain valid after reset.\n\n### PoC\n#### Case 1: Password reset does not revoke existing session\n\n1. Create or use a normal user account.\n2. Log in as that user and save the authenticated session cookie.\n3. Trigger forgot-password for the account.\n4. Use the emailed reset link and set a new password.\n5. Verify:\n   - the old password no longer works\n   - the new password works\n6. Replay the **old pre-reset session cookie** against an authenticated endpoint such as `/api/profile`.\n\nExample validation request:\n```http\nGET /api/profile HTTP/1.1\nHost: 127.0.0.1:9000\nCookie: session=\u003cold_pre_reset_session\u003e\n```\n\nObserved result:\n\nServer returns `HTTP/1.1 200 OK`\nResponse contains the authenticated user profile\n\n#### Case 2: Password change does not revoke other active sessions\n\n1. Log in twice as the same user and save two authenticated session cookies:\n   - session A\n   - session B\n\n2. Using session A, change the password through the authenticated profile update endpoint.\n\n3. Verify:\n   - the old password no longer works\n   - the new password works\n\n4. Replay session B against an authenticated endpoint such as `/api/profile`.\n\nExample password change request:\n```http\nPUT /api/profile HTTP/1.1\nHost: 127.0.0.1:9000\nCookie: session=\u003csession_A\u003e\nContent-Type: application/json\n\n{\n  \"name\":\"victim1\",\n  \"email\":\"victim1@test.local\",\n  \"password\":\"VictimChanged123\"\n}\n```\n\nThen validate session B:\n```http\nGET /api/profile HTTP/1.1\nHost: 127.0.0.1:9000\nCookie: session=\u003csession_B\u003e\n```\n\nObserved result:\n- Server returns `HTTP/1.1 200 OK`\n- Response contains the authenticated user profile\n\n## Impact\n\nThis issue allows persistence of unauthorized access after credential recovery actions.\n\nIf an attacker has already stolen a valid session cookie through any means (for example malware, browser compromise, XSS, shared machine access, proxy leakage, or other session theft), the victim cannot fully recover the account by changing or resetting the password alone. The attacker\u2019s existing session remains valid.\n\nThis impacts account recovery expectations and session security for all authenticated users, including users with TOTP enabled.\n\n## Attachment\n[listmonk-session-report.zip](https://github.com/user-attachments/files/25975979/listmonk-session-report.zip)",
  "id": "GHSA-h5j9-cvrw-v5qh",
  "modified": "2026-04-06T17:25:20Z",
  "published": "2026-04-01T23:48:43Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/knadh/listmonk/security/advisories/GHSA-h5j9-cvrw-v5qh"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-34828"
    },
    {
      "type": "WEB",
      "url": "https://github.com/knadh/listmonk/commit/db82035d619348949512dafdaf60c86037cafc9e"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/knadh/listmonk"
    },
    {
      "type": "WEB",
      "url": "https://github.com/knadh/listmonk/releases/tag/v6.1.0"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "listmonk\u0027s active sessions remain valid after password reset and password change"
}

GHSA-H5WQ-J227-WJWH

Vulnerability from github – Published: 2026-03-21 00:31 – Updated: 2026-05-06 15:32
VLAI
Details

The WebSocket backend uses charging station identifiers to uniquely associate sessions but allows multiple endpoints to connect using the same session identifier. This implementation results in predictable session identifiers and enables session hijacking or shadowing, where the most recent connection displaces the legitimate charging station and receives backend commands intended for that station. This vulnerability may allow unauthorized users to authenticate as other users or enable a malicious actor to cause a denial-of-service condition by overwhelming the backend with valid session requests.

Severity
7.3 (High)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
6.9 (Medium)
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2026-27649"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-613"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-03-20T23:16:43Z",
    "severity": "MODERATE"
  },
  "details": "The WebSocket backend uses charging station identifiers to uniquely associate sessions but allows\u00a0multiple endpoints to connect using the same session identifier. This implementation results in predictable session identifiers and enables session hijacking or shadowing, where the most recent connection displaces the legitimate charging station and receives backend commands intended for that station. This vulnerability may allow unauthorized users to authenticate as other users or enable a malicious actor to cause a denial-of-service condition by overwhelming the backend with valid session requests.",
  "id": "GHSA-h5wq-j227-wjwh",
  "modified": "2026-05-06T15:32:32Z",
  "published": "2026-03-21T00:31:43Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-27649"
    },
    {
      "type": "WEB",
      "url": "https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-078-06.json"
    },
    {
      "type": "WEB",
      "url": "https://www.cisa.gov/news-events/ics-advisories/icsa-26-078-06"
    },
    {
      "type": "WEB",
      "url": "https://www.ctek.com/support"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L",
      "type": "CVSS_V3"
    },
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
      "type": "CVSS_V4"
    }
  ]
}

GHSA-H6G4-MV38-WH4G

Vulnerability from github – Published: 2022-10-17 19:00 – Updated: 2025-05-13 18:30
VLAI
Details

devhub 0.102.0 was discovered to contain a broken session control.

Severity
5.4 (Medium)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2022-41542"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-613"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2022-10-17T14:15:00Z",
    "severity": "MODERATE"
  },
  "details": "devhub 0.102.0 was discovered to contain a broken session control.",
  "id": "GHSA-h6g4-mv38-wh4g",
  "modified": "2025-05-13T18:30:40Z",
  "published": "2022-10-17T19:00:29Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-41542"
    },
    {
      "type": "WEB",
      "url": "https://app.devhubapp.com"
    },
    {
      "type": "WEB",
      "url": "https://devhubapp.com"
    },
    {
      "type": "WEB",
      "url": "https://medium.com/%40sc0p3hacker/cve-2022-41542-session-mis-configuration-in-devhub-application-ca956bb9027a"
    },
    {
      "type": "WEB",
      "url": "https://medium.com/@sc0p3hacker/cve-2022-41542-session-mis-configuration-in-devhub-application-ca956bb9027a"
    },
    {
      "type": "WEB",
      "url": "http://devhub.com"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-H7VV-46P5-PRMH

Vulnerability from github – Published: 2023-04-05 18:30 – Updated: 2023-04-05 21:28
VLAI
Summary
Firefly III insufficiently expires sessions
Details

Firefly III prior to 6.0.0 insufficiently expires sessions upon close.

Severity
4.2 (Medium)
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "grumpydictator/firefly-iii"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.0.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2023-1788"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-613"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2023-04-05T21:28:05Z",
    "nvd_published_at": "2023-04-05T16:15:00Z",
    "severity": "MODERATE"
  },
  "details": "Firefly III prior to 6.0.0 insufficiently expires sessions upon close.",
  "id": "GHSA-h7vv-46p5-prmh",
  "modified": "2023-04-05T21:28:05Z",
  "published": "2023-04-05T18:30:18Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-1788"
    },
    {
      "type": "WEB",
      "url": "https://github.com/firefly-iii/firefly-iii/commit/68f398f97cbe1870fc098d8460bf903b9c3fab30"
    },
    {
      "type": "WEB",
      "url": "https://github.com/firefly-iii/firefly-iii"
    },
    {
      "type": "WEB",
      "url": "https://huntr.dev/bounties/79323c9e-e0e5-48ef-bd19-d0b09587ccb2"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Firefly III insufficiently expires sessions"
}

GHSA-H8Q5-VXRG-QGMF

Vulnerability from github – Published: 2026-04-22 18:31 – Updated: 2026-04-22 18:31
VLAI
Details

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that could have allowed a user to use invalidated or incorrectly scoped credentials to access Virtual Registries under certain conditions.

Severity
5.4 (Medium)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2026-6515"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-613"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-04-22T17:16:44Z",
    "severity": "MODERATE"
  },
  "details": "GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that could have allowed a user to use invalidated or incorrectly scoped credentials to access Virtual Registries under certain conditions.",
  "id": "GHSA-h8q5-vxrg-qgmf",
  "modified": "2026-04-22T18:31:46Z",
  "published": "2026-04-22T18:31:46Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-6515"
    },
    {
      "type": "WEB",
      "url": "https://about.gitlab.com/releases/2026/04/22/patch-release-gitlab-18-11-1-released"
    },
    {
      "type": "WEB",
      "url": "https://gitlab.com/gitlab-org/gitlab/-/work_items/595993"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-H998-HXXJ-8Q83

Vulnerability from github – Published: 2026-06-22 15:30 – Updated: 2026-09-15 19:51
VLAI
Summary
Mattermost doesn't invalidate cached authentication state for active WebSocket connections during global session revocation
Details

Mattermost versions 11.7.x <= 11.7.0, 11.6.x <= 11.6.2, 11.5.x <= 11.5.5, 10.11.x <= 10.11.17 fail to invalidate cached authentication state for active WebSocket connections during global session revocation, which allows a user with an existing WebSocket connection to remain authenticated and continue receiving real-time events until the cached session expires or the client reconnects.. Mattermost Advisory ID: MMSA-2026-00664

Severity
4.3 (Medium)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/mattermost/mattermost-server"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "11.7.0"
            },
            {
              "fixed": "11.7.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/mattermost/mattermost-server"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "11.6.0"
            },
            {
              "fixed": "11.6.3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/mattermost/mattermost-server"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "11.5.0"
            },
            {
              "fixed": "11.5.6"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/mattermost/mattermost-server"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "10.11.0"
            },
            {
              "fixed": "10.11.18"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-9162"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-613"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-09-15T19:51:33Z",
    "nvd_published_at": "2026-06-22T14:17:55Z",
    "severity": "MODERATE"
  },
  "details": "Mattermost versions 11.7.x \u003c= 11.7.0, 11.6.x \u003c= 11.6.2, 11.5.x \u003c= 11.5.5, 10.11.x \u003c= 10.11.17 fail to invalidate cached authentication state for active WebSocket connections during global session revocation, which allows a user with an existing WebSocket connection to remain authenticated and continue receiving real-time events until the cached session expires or the client reconnects.. Mattermost Advisory ID: MMSA-2026-00664",
  "id": "GHSA-h998-hxxj-8q83",
  "modified": "2026-09-15T19:51:33Z",
  "published": "2026-06-22T15:30:46Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-9162"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/mattermost/mattermost"
    },
    {
      "type": "WEB",
      "url": "https://mattermost.com/security-updates"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Mattermost doesn\u0027t invalidate cached authentication state for active WebSocket connections during global session revocation"
}

GHSA-H9Q8-5GV2-V6MG

Vulnerability from github – Published: 2021-03-12 23:09 – Updated: 2026-02-02 21:01
VLAI
Summary
Potential Session Hijacking
Details

Impact

Potential session hijacking of store customers.

Patches

We recommend to update to the current version 6.3.5.2. You can get the update to 6.3.5.2 regularly via the Auto-Updater or directly via the download overview.

https://www.shopware.com/en/download/#shopware-6

Workarounds

For older versions of 6.1 and 6.2, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.

https://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659

For more information

https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-03-2021

Show details on source website
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 6.3.5.1"
      },
      "package": {
        "ecosystem": "Packagist",
        "name": "shopware/platform"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.3.5.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2021-32710"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-613"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2021-03-12T22:10:34Z",
    "nvd_published_at": null,
    "severity": "LOW"
  },
  "details": "### Impact\nPotential session hijacking of store customers.\n\n### Patches\nWe recommend to update to the current version 6.3.5.2. You can get the update to 6.3.5.2 regularly via the Auto-Updater or directly via the download overview.\n\nhttps://www.shopware.com/en/download/#shopware-6\n\n### Workarounds\nFor older versions of 6.1 and 6.2, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.\n\nhttps://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659\n\n### For more information\nhttps://docs.shopware.com/en/shopware-6-en/security-updates/security-update-03-2021",
  "id": "GHSA-h9q8-5gv2-v6mg",
  "modified": "2026-02-02T21:01:07Z",
  "published": "2021-03-12T23:09:08Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/shopware/platform/security/advisories/GHSA-h9q8-5gv2-v6mg"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2021-32710"
    },
    {
      "type": "WEB",
      "url": "https://github.com/shopware/platform/commit/010c0154bea57c1fca73277c7431d029db7a972e"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/shopware/shopware"
    },
    {
      "type": "WEB",
      "url": "https://packagist.org/packages/shopware/platform"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [],
  "summary": "Potential Session Hijacking"
}

GHSA-HGX3-J7FM-PJM3

Vulnerability from github – Published: 2025-12-01 18:30 – Updated: 2025-12-01 21:30
VLAI
Details

nopCommerce v4.70 and prior, and version 4.80.3, does not invalidate session cookies after logout or session termination, allowing an attacker who has a a valid session cookie access to privileged endpoints (such as /admin) even after the legitimate user has logged out, enabling session hijacking. Any version above 4.70 that is not 4.80.3 fixes the vulnerability.

Severity
7.1 (High)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:N
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2025-11699"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-613"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-12-01T16:15:51Z",
    "severity": "HIGH"
  },
  "details": "nopCommerce v4.70 and prior, and version 4.80.3, does not invalidate session cookies after logout or session termination, allowing an attacker who has a \na valid session cookie access to privileged endpoints (such as /admin) even after the legitimate user has logged out, enabling session hijacking. Any version above 4.70 that is not 4.80.3 fixes the vulnerability.",
  "id": "GHSA-hgx3-j7fm-pjm3",
  "modified": "2025-12-01T21:30:26Z",
  "published": "2025-12-01T18:30:37Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-11699"
    },
    {
      "type": "WEB",
      "url": "https://github.com/nopSolutions/nopCommerce/issues/7044"
    },
    {
      "type": "WEB",
      "url": "https://seclists.org/fulldisclosure/2025/Aug/14"
    },
    {
      "type": "WEB",
      "url": "https://www.kb.cert.org/vuls/id/633103"
    },
    {
      "type": "WEB",
      "url": "https://www.nopcommerce.com/en/release-notes?srsltid=AfmBOoravPKjN19pm_XZbXZ7GvPhkt8cxlK6794BJRZlY5RxJU_yNoTT"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:N",
      "type": "CVSS_V3"
    }
  ]
}
Mitigation
Implementation

Set sessions/credentials expiration date.

No CAPEC attack patterns related to this CWE.

← Back to the CWE list