CVE-2026-108904 ph7software CVE debrief

Who should care

Defenders responsible for pH7Builder deployments, API security, and sensitive data protection should assess exposure and prioritize remediation. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify exposure and implement protective measures to prevent account takeovers and unauthorized access to sensitive member data.

Why it matters

Defenders should prioritize verifying exposure and assessing potential impact, focusing on API key management and sensitive data protection, due to the information disclosure vulnerability in pH7Builder before 18.5.0.

• Potential unauthorized access to sensitive member data
• Possible account takeover and bypass of two-factor authentication
• Need for verification of API key management and sensitive data protection

Technical summary

pH7Builder before 18.5.0 contains an information disclosure vulnerability in the UserController, allowing API clients to obtain sensitive member data, including bcrypt password hashes, non-expiring hashValidation reset tokens, and TOTP secrets. The vulnerability is caused by the UserController::users() and user() returning unfiltered database rows. Attackers holding a valid private API key can exploit this vulnerability to take over accounts and bypass two-factor authentication. Defenders should prioritize verifying exposure and assessing potential impact, focusing on API key management and sensitive data protection.

Defensive priority

Defenders should prioritize verifying exposure and assessing potential impact, focusing on API key management and sensitive data protection.

Recommended defensive actions

• Verify pH7Builder version and assess exposure
• Restrict API access and validate API keys
• Implement additional logging and monitoring for API activity
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the information disclosure vulnerability in pH7Builder before 18.5.0, allowing API clients to obtain sensitive member data. The vulnerability is caused by the UserController::users() and user() returning unfiltered database rows. Attackers holding a valid private API key can retrieve bcrypt password hashes, non-expiring hashValidation reset tokens, and TOTP secrets to take over accounts and bypass two-factor authentication. Defenders should verify exposure and assess potential impact,

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.