Credential disclosure via committed environment-example token
Published Jan 13, 2025 · Updated Jan 13, 2025
Cleartext credential exposure in Vercel next-forge before 3.0.11 allows remote attackers to obtain a BaseHub access token. The apps/web/.env.example template stores a populated BASEHUB_TOKEN value instead of an empty placeholder, so repository and generated-project copies disclose the credential. Exposure requires access to an affected template or a project derived from it, and the token grants only the BaseHub access authorized to that credential.
Summary
What happened
Cleartext credential exposure in Vercel next-forge before 3.0.11 allows remote attackers to obtain a BaseHub access token. The apps/web/.env.example template stores a populated BASEHUB_TOKEN value instead of an empty placeholder, so repository and generated-project copies disclose the credential. Exposure requires access to an affected template or a project derived from it, and the token grants only the BaseHub access authorized to that credential.
The record
- CVE
- CVE-2025-23027
- Published
- Jan 13, 2025
- Updated
- Jan 13, 2025
- Vendor
- Vercel
- Product
- next-forge
- Classifications
- CWE-312, CAPEC-37, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 13, 2025CVE publishedPublication date reported by the CVE source.
- Jan 13, 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=< 3.0.11
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