CVE-2020-24130

8.1 HIGH

📋 TL;DR

This CSRF vulnerability in Ponzu CMS 0.11.0 allows attackers to trick authenticated users into performing unauthorized actions through malicious requests. Attackers can change user/admin credentials and add/delete administrator accounts without the victim's knowledge. All Ponzu 0.11.0 installations with the configure.html component accessible are affected.

💻 Affected Systems

Products:
  • Ponzu CMS
Versions: 0.11.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects installations with configure.html component accessible. Earlier versions may also be vulnerable but not confirmed.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of the CMS instance with attacker gaining administrative control, data manipulation, and potential lateral movement to connected systems.

🟠

Likely Case

Unauthorized account creation or credential changes leading to privilege escalation and data breaches.

🟢

If Mitigated

Limited impact if proper CSRF protections are implemented or if the vulnerable component is not internet-facing.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires the victim to be authenticated and visit a malicious page while logged into Ponzu. No authentication bypass needed.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 0.11.1 or later

Vendor Advisory: https://github.com/ponzu-cms/ponzu/issues/352

Restart Required: Yes

Instructions:

1. Backup current installation. 2. Update Ponzu to version 0.11.1 or later. 3. Restart the Ponzu service. 4. Verify the fix by checking version and testing CSRF protections.

🔧 Temporary Workarounds

CSRF Token Implementation

all

Manually add CSRF tokens to configure.html forms

Modify configure.html to include CSRF tokens in all forms and validate them server-side

Access Restriction

all

Restrict access to configure.html component

Configure web server (nginx/apache) to restrict access to /admin/configure.html to trusted IPs only

🧯 If You Can't Patch

  • Implement strict SameSite cookie policies and CORS restrictions
  • Use web application firewall (WAF) rules to detect and block CSRF attempts

🔍 How to Verify

Check if Vulnerable:

Check if running Ponzu version 0.11.0 and if configure.html endpoint is accessible without CSRF tokens

Check Version:

ponzu version

Verify Fix Applied:

Verify Ponzu version is 0.11.1+ and test that configure.html forms now require valid CSRF tokens

📡 Detection & Monitoring

Log Indicators:

  • Multiple failed authentication attempts followed by successful configure.html access
  • Unusual account creation or credential change events

Network Indicators:

  • Requests to configure.html without proper referrer headers or CSRF tokens
  • Cross-origin requests to administrative endpoints

SIEM Query:

source="ponzu" AND (uri="/admin/configure.html" OR event="account_creation" OR event="password_change")

🔗 References

📤 Share & Export