Username change via activate-account path traversal
Published Feb 4, 2025 · Updated Feb 11, 2025
Client-side path traversal in Discourse beta and tests-passed through 3.4.0.beta3 allows remote attackers to change a target user’s username. The vendor advisory identifies the activate-account route but does not disclose how its client-side path handling converts a crafted link into a username update. Exploitation requires the target user to follow the link; the documented consequence is limited to alteration of that user’s own username.
Summary
What happened
Client-side path traversal in Discourse beta and tests-passed through 3.4.0.beta3 allows remote attackers to change a target user’s username. The vendor advisory identifies the activate-account route but does not disclose how its client-side path handling converts a crafted link into a username update. Exploitation requires the target user to follow the link; the documented consequence is limited to alteration of that user’s own username.
The record
- CVE
- CVE-2025-22601
- Published
- Feb 4, 2025
- Updated
- Feb 11, 2025
- Vendor
- Discourse
- Product
- Discourse
- Classifications
- CWE-22, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 4, 2025CVE publishedPublication date reported by the CVE source.
- Feb 11, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=beta: <= 3.4.0.beta3
- Affected versionversion=tests-passed: <= 3.4.0.beta3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo