CVE-2025-69768
SQL Injection in Chyrp Admin.php Exposes Sensitive Data
Publication date: 2026-03-16
Last updated on: 2026-03-20
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| chyrp | chyrp | to 2.5.2 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': "CVE-2025-69768 is an authenticated SQL Injection vulnerability in Chyrp CMS version 2.5.2 and earlier. It occurs in the Admin.php component where the application constructs SQL queries by directly concatenating the user-controlled POST parameter 'prefix' into the table name without any input validation or sanitization."}, {'type': 'paragraph', 'content': "Because the 'prefix' parameter is inserted directly into the SQL query string, an attacker with administrative access can inject arbitrary SQL code. This allows the attacker to manipulate the database by reading sensitive information, modifying or deleting records, or causing denial of service."}, {'type': 'paragraph', 'content': 'The vulnerability arises from building SQL queries using string concatenation rather than using parameterized queries or prepared statements, which would treat user input strictly as data and prevent injection.'}] [3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive information stored in the database.
An attacker with administrative access can execute arbitrary SQL commands, which may lead to data modification or deletion, potentially causing data loss or corruption.
It can also result in denial of service by dropping critical tables or otherwise disrupting the database.
Depending on the database permissions, it might even allow execution of remote code or further compromise of the system.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': "This SQL Injection vulnerability in Chyrp CMS occurs via the POST parameter 'prefix' in the admin.php component. Detection involves monitoring or testing for malicious SQL injection attempts targeting this parameter."}, {'type': 'paragraph', 'content': "One way to detect this vulnerability is by sending crafted POST requests to the admin.php endpoint with various payloads in the 'prefix' parameter to see if the system is vulnerable to SQL injection."}, {'type': 'list_item', 'content': 'Use curl to send a test POST request with a benign payload to check response behavior: curl -X POST -d "prefix=test" https://your-chyrp-site/admin.php'}, {'type': 'list_item', 'content': 'Send a crafted payload to test for SQL injection, for example: curl -X POST -d "prefix=abc; DROP TABLE users; --" https://your-chyrp-site/admin.php and observe if the response indicates an error or unexpected behavior.'}, {'type': 'list_item', 'content': "Monitor web server logs for suspicious POST requests containing SQL keywords or unusual characters in the 'prefix' parameter."}, {'type': 'list_item', 'content': 'Use a web application scanner or SQL injection detection tools that can test POST parameters for injection vulnerabilities.'}] [3]
What immediate steps should I take to mitigate this vulnerability?
[{'type': 'paragraph', 'content': 'To mitigate the SQL Injection vulnerability in Chyrp CMS, immediate steps include:'}, {'type': 'list_item', 'content': 'Avoid building SQL queries by concatenating user input directly. Instead, implement parameterized queries or prepared statements to ensure user input is treated as data.'}, {'type': 'list_item', 'content': "Enforce strict input validation on the 'prefix' parameter, allowing only alphanumeric characters via regex or similar methods, rejecting any input that does not conform."}, {'type': 'list_item', 'content': "Limit the database user's permissions to the minimum necessary, avoiding privileges like DROP, CREATE, ALTER, or GRANT to reduce potential damage if an injection occurs."}, {'type': 'list_item', 'content': 'Deploy a Web Application Firewall (WAF) to detect and block common SQL injection patterns as a defense-in-depth measure.'}, {'type': 'list_item', 'content': 'If possible, update or patch the Chyrp CMS to a version where this vulnerability is fixed.'}] [3]