API credential disclosure via public drupalSettings
Published Sep 2, 2026 · Updated Sep 2, 2026
Information disclosure in DXPR Builder before 2.8.1 allows remote attackers to read an API credential through public page responses. The 2.x module places its licensing and AI-services JSON Web Token in drupalSettings without restricting that JavaScript configuration to authorized visitors. Exposure requires AI agent features to be enabled and configured with an API token; anonymous visitors can obtain the token and its associated service access.
Summary
What happened
Information disclosure in DXPR Builder before 2.8.1 allows remote attackers to read an API credential through public page responses. The 2.x module places its licensing and AI-services JSON Web Token in drupalSettings without restricting that JavaScript configuration to authorized visitors. Exposure requires AI agent features to be enabled and configured with an API token; anonymous visitors can obtain the token and its associated service access.
The record
- CVE
- CVE-2026-81162
- Published
- Sep 2, 2026
- Updated
- Sep 2, 2026
- Vendor
- DXPR
- Product
- DXPR Builder
- Classifications
- CWE-201, CAPEC-87, T1552
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 2, 2026CVE publishedPublication date reported by the CVE source.
- Sep 2, 2026Record 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=0.0.0 <2.8.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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