CVE-2024-25417

8.8 HIGH

📋 TL;DR

Flusity-CMS v2.33 contains a CSRF vulnerability in the translation management component that allows attackers to trick authenticated administrators into performing unauthorized actions. This affects all Flusity-CMS installations running version 2.33 with the vulnerable endpoint accessible. Attackers can exploit this to modify translations or potentially perform other administrative actions.

💻 Affected Systems

Products:
  • flusity-CMS
Versions: v2.33
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects installations with the /core/tools/add_translation.php endpoint accessible and administrators who can be tricked into visiting malicious pages.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could modify all translations, inject malicious content, or chain with other vulnerabilities to achieve full system compromise.

🟠

Likely Case

Attackers modify translations to insert malicious content, deface websites, or redirect users to phishing sites.

🟢

If Mitigated

With proper CSRF protections, the vulnerability is neutralized and no unauthorized actions can be performed.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

CSRF attacks are well-understood and easy to weaponize. Exploitation requires the victim to be authenticated as an administrator.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None available

Restart Required: No

Instructions:

No official patch available. Consider upgrading to a newer version if available or implementing workarounds.

🔧 Temporary Workarounds

Implement CSRF Tokens

all

Add CSRF protection tokens to the /core/tools/add_translation.php endpoint

Edit /core/tools/add_translation.php to include CSRF token validation

Restrict Access

all

Restrict access to the vulnerable endpoint using IP whitelisting or authentication

Add .htaccess rules or web server configuration to restrict /core/tools/

🧯 If You Can't Patch

  • Implement strict SameSite cookie policies and require re-authentication for sensitive actions
  • Use web application firewalls (WAF) with CSRF protection rules

🔍 How to Verify

Check if Vulnerable:

Check if /core/tools/add_translation.php exists and lacks CSRF protection by reviewing the source code

Check Version:

Check CMS version in configuration files or admin panel

Verify Fix Applied:

Verify that CSRF tokens are properly implemented and validated in the endpoint

📡 Detection & Monitoring

Log Indicators:

  • Multiple POST requests to /core/tools/add_translation.php from different referrers
  • Translation modifications without corresponding admin login events

Network Indicators:

  • HTTP requests to /core/tools/add_translation.php with suspicious referrer headers

SIEM Query:

source="web_server" AND (url="/core/tools/add_translation.php" AND method="POST") | stats count by src_ip, referrer

🔗 References

📤 Share & Export