Skip to main content
DashboardThreatsMapFeedsAPI
reconnecting
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-5433: SQL Injection in Fengoffice Feng Office

0
Medium
VulnerabilityCVE-2025-5433cvecve-2025-5433
Published: Mon Jun 02 2025 (06/02/2025, 06:31:04 UTC)
Source: CVE Database V5
Vendor/Project: Fengoffice
Product: Feng Office

Description

A vulnerability was found in Fengoffice Feng Office 3.5.1.5 and classified as critical. Affected by this issue is some unknown functionality of the file /index.php?c=account&a=set_timezone. The manipulation of the argument tz_offset leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

AI-Powered Analysis

AILast updated: 07/09/2025, 12:41:17 UTC

Technical Analysis

CVE-2025-5433 is a SQL Injection vulnerability identified in Fengoffice Feng Office version 3.5.1.5, specifically within the /index.php?c=account&a=set_timezone endpoint. The vulnerability arises from improper sanitization of the 'tz_offset' parameter, which can be manipulated by an attacker to inject malicious SQL code. This injection flaw allows an unauthenticated remote attacker with low privileges (PR:L) to execute arbitrary SQL commands on the backend database without requiring user interaction. The vulnerability affects confidentiality, integrity, and availability of the affected system, as attackers could potentially extract sensitive data, modify or delete records, or disrupt service availability. The CVSS 4.0 base score is 5.3 (medium severity), reflecting that while the attack vector is network-based and requires no user interaction, it does require some level of privileges (low privileges) and has limited impact on confidentiality, integrity, and availability. The vendor has not responded to the disclosure, and no official patch or mitigation guidance has been published yet. Although no known exploits are currently reported in the wild, public disclosure of the exploit code increases the risk of exploitation. Given the nature of Feng Office as a collaborative project management and office suite platform, exploitation could lead to unauthorized access to project data, user information, and potentially sensitive business documents stored within the system.

Potential Impact

For European organizations using Feng Office 3.5.1.5, this vulnerability poses a significant risk to the confidentiality and integrity of their project management and collaboration data. Successful exploitation could lead to data breaches involving sensitive business information, unauthorized data manipulation, or service disruption. This is particularly critical for sectors handling regulated or sensitive data such as finance, healthcare, legal, and government entities. The ability to remotely exploit this vulnerability without user interaction increases the attack surface, especially for organizations exposing Feng Office to the internet. Additionally, the lack of vendor response and absence of patches means organizations must rely on internal mitigations, increasing operational risk. The medium CVSS score suggests moderate risk, but the real-world impact could be higher depending on the deployment context and data sensitivity. Organizations could face compliance issues under GDPR if personal data is compromised, leading to potential legal and reputational consequences.

Mitigation Recommendations

Given the absence of an official patch, European organizations should implement immediate compensating controls. These include: 1) Restricting external access to the Feng Office application by using network-level controls such as VPNs, IP whitelisting, or firewall rules to limit exposure. 2) Implementing web application firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the 'tz_offset' parameter. 3) Conducting thorough input validation and sanitization at the application or proxy level if possible, to filter malicious payloads. 4) Monitoring application logs for unusual database errors or suspicious activity related to the vulnerable endpoint. 5) Planning and prioritizing an upgrade or patch deployment once the vendor releases a fix or considering alternative project management solutions if a timely patch is unavailable. 6) Educating internal security teams about this vulnerability to enhance incident detection and response capabilities. 7) Regularly backing up critical data to enable recovery in case of data integrity compromise.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulDB
Date Reserved
2025-06-01T10:55:38.487Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 683d47f3182aa0cae237a96c

Added to database: 6/2/2025, 6:42:59 AM

Last enriched: 7/9/2025, 12:41:17 PM

Last updated: 10/7/2025, 1:46:31 PM

Views: 23

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats