CSRF Token Reuse Vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.6 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:L

EPSS

• CVE-2023-45128: 0.36% estimated exploitation activity in the next 30 days; percentile 30.33 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A Cross-Site Request Forgery (CSRF) vulnerability has been identified in the application, which allows an attacker to inject arbitrary values and forge malicious requests on behalf of a user. This vulnerability can allow an attacker to inject arbitrary values without any authentication, or perform various malicious actions on behalf of an authenticated user, potentially compromising the security and integrity of the application. Vulnerability Details The vulnerability is caused by improper validation and enforcement of CSRF tokens within the application. The following issues were identified: 1. Token Injection: For 'safe' methods, the token was extracted from the cookie and saved to storage without further validation or sanitization. 2. Lack of Token Association: The CSRF token was validated against tokens in storage but not associated with a session, nor by using a Double Submit Cookie Method, allowing for token reuse. Specific Go Packages Affected…

Published by the source

17 Oct 2023, 12:40 UTC

Last modified by the source

11 Nov 2023, 05:01 UTC

Source last checked

26 Oct 2026, 15:00 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-94w9-97p3-p368

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-45128

Advisory: CSRF Token Reuse Vulnerability
IDs: CVE-2023-45128, GHSA-94w9-97p3-p368
Record: https://patchnext.com/advisories/cve-2023-45128 (revision 1, source checked 26 Oct 2026, 15:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/gofiber/fiber/v2 2.50.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/gofiber/fiber/v2: affected < 2.50.0; fixed in 2.50.0

## Suggested inspection (read-only)
- Go github.com/gofiber/fiber/v2: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/gofiber/fiber/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-94w9-97p3-p368 (GitHub-reviewed advisory GHSA-94w9-97p3-p368 lists affected ranges: Go github.com/gofiber/fiber/v2 >=0 <2.50.0)

Commands are suggestions: review each one before running it.