Phishing redirects via reflected domain-field HTML
Published Jun 2, 2025 · Updated Jun 2, 2025
HTML injection in Froxlor before 2.2.6 allows remote authenticated users to place deceptive links in customer-portal error pages. The SubDomains API get method inserted the user-controlled domainname value into a not-found exception that was rendered without safe output handling. A customer account can submit the crafted domain value, but another user must view the resulting error page and follow the injected link for phishing or credential theft.
Summary
What happened
HTML injection in Froxlor before 2.2.6 allows remote authenticated users to place deceptive links in customer-portal error pages. The SubDomains API get method inserted the user-controlled domainname value into a not-found exception that was rendered without safe output handling. A customer account can submit the crafted domain value, but another user must view the resulting error page and follow the injected link for phishing or credential theft.
The record
- CVE
- CVE-2025-48958
- Published
- Jun 2, 2025
- Updated
- Jun 2, 2025
- Vendor
- Froxlor
- Product
- Froxlor
- Classifications
- CWE-79, T1566.002
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 2, 2025CVE publishedPublication date reported by the CVE source.
- Jun 2, 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=< 2.2.6
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
- Upstream domain-field HTML-injection proof of conceptproof of concept · demonstrated
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