CVE-2026-90495
7.3Fengoffice · Feng Office
A SQL injection vulnerability in the Feng Office Legacy API allows unauthenticated remote attackers to manipulate the auth argument in the Contacts::instance->findAll function.
Executive summary
A high-severity SQL injection vulnerability in Feng Office poses a significant risk to data integrity and confidentiality due to the availability of a public exploit.
Vulnerability
This flaw is a classic SQL injection (CWE-89) located in the application/models/CompanyWebsite.class.php file. An unauthenticated attacker can supply malicious input to the auth parameter within the Legacy API to execute arbitrary database queries.
Business impact
Successful exploitation of this vulnerability allows unauthorized actors to interact directly with the underlying database, potentially leading to the theft of sensitive business information or unauthorized modification of records. With a CVSS score of 7.3, this issue is considered high-risk, especially given the remote, unauthenticated nature of the attack vector which lowers the barrier to entry for malicious actors.
Remediation
Immediate Action: Since no official patch is currently available, administrators should restrict access to the Legacy API component or disable it entirely if it is not required for business operations.
Proactive Monitoring: Review web application logs for suspicious patterns in the auth parameter, specifically looking for SQL syntax characters such as single quotes, semicolons, or comment indicators.
Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block common SQL injection payloads targeting the application/models/CompanyWebsite.class.php endpoint.
Exploitation status
Public Exploit Available: Yes, a public proof-of-concept exists as documented in the research write-up referenced in the vulnerability record.
Analyst recommendation
Given the public availability of an exploit and the vendor's lack of response, this vulnerability presents an immediate risk to the environment. Security teams must prioritize isolating the affected component and implementing compensating controls to prevent unauthorized database access until an official security update is released.
History
- Disclosed CVE record published
- Collected by CVE Brief via github
- Analyst report written
- Published in the daily brief high section
Sources
Originally found and disclosed by ciphersecuritylabs (VulDB User), with VulDB CNA Team (coordinator), per the CVE Program record.
- VDB-403083 | Fengoffice Feng Office Legacy API CompanyWebsite.class.php instance->findAll sql injection Vulnerability database entry
- VDB-403083 | CTI Indicators (IOB, IOC, TTP, IOA)
- CVE-2026-90495 | CVE Analysis and Report Third-party advisory
- Submit #892871 | Feng Office Feng Office Community Edition 3.11.13.11 SQL Injection Third-party advisory
- Exploit / PoC