Apostrophe has a Weak Password Recovery Mechanism for Forgotten Password and Improper Input Validation

Exploitation

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

CVSS

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

EPSS

• CVE-2026-45013: 0.30% estimated exploitation activity in the next 30 days; percentile 23.32 (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.

Summary ApostropheCMS's password reset flow constructs the reset URL using req.hostname, which is derived directly from the attacker-controlled HTTP Host header when apos.baseUrl is not explicitly configured. An unauthenticated attacker who knows a victim's email address can send a crafted reset request that causes the application to email the victim a reset link pointing to the attacker's domain. When the victim clicks the link, the valid reset token is delivered to the attacker, enabling full account takeover. Affected Component modules/@apostrophecms/login/index.js — resetRequest route Precondition: passwordReset: true is set and apos.baseUrl is not configured. Vulnerability Details The setPrefixUrls middleware (i18n layer) builds req.baseUrl using req.hostname: The resetRequest handler then passes this tainted value directly into URL construction: When apos.baseUrl is configured, it is used unconditionally and the attacker's Host header is ignored — that path is not vulnerable.…

Published by the source

14 May 2026, 18:27 UTC

Last modified by the source

12 Jun 2026, 22:15 UTC

Source last checked

26 Oct 2026, 12:55 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-gf43-24g3-5hw2

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-gf43-24g3-5hw2

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

# Patch Next advisory brief: CVE-2026-45013

Advisory: Apostrophe has a Weak Password Recovery Mechanism for Forgotten Password and Improper Input Validation
IDs: CVE-2026-45013, GHSA-gf43-24g3-5hw2
Record: https://patchnext.com/advisories/cve-2026-45013 (revision 2, source checked 26 Oct 2026, 12:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm apostrophe: affected <= 4.29.0

## Suggested inspection (read-only)
- `npm ls apostrophe --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on apostrophe.
- 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://osv.dev/vulnerability/GHSA-gf43-24g3-5hw2 (OSV record GHSA-gf43-24g3-5hw2 lists affected ranges: npm apostrophe >=0 <=4.29.0)
- Verified: https://github.com/advisories/GHSA-gf43-24g3-5hw2 (GitHub-reviewed advisory GHSA-gf43-24g3-5hw2 lists affected ranges: npm apostrophe >=0 <=4.29.0)

Commands are suggestions: review each one before running it.