CVE-2020-37186
Awaiting Analysis Awaiting Analysis - Queue
Remote Code Execution in Chevereto 3.13.4 via DB Prefix Injection

Publication date: 2026-02-11

Last updated on: 2026-02-12

Assigner: VulnCheck

Description
Chevereto 3.13.4 Core contains a remote code execution vulnerability that allows attackers to inject malicious code during database configuration installation. Attackers can manipulate the database table prefix parameter to write a PHP shell file and execute arbitrary system commands through a crafted POST request.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-11
Last Modified
2026-02-12
Generated
2026-05-07
AI Q&A
2026-02-11
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 3 associated CPEs
Vendor Product Version / Range
chevereto chevereto-free to 1.1.4 (exc)
chevereto chevereto-free 1.6.2
chevereto chevereto 3.13.4
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-94 The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability impact me? :

This vulnerability can have severe impacts including unauthorized remote code execution on the affected server. An attacker can gain control over the system by executing arbitrary system commands, potentially leading to data theft, server compromise, or further attacks within the network.

Because the exploit requires no authentication or user interaction, it poses a high risk of exploitation, making affected systems highly vulnerable to attackers.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


Can you explain this vulnerability to me?

CVE-2020-37186 is a critical remote code execution vulnerability in Chevereto Core version 3.13.4 and earlier. It occurs during the database configuration installation process, where an attacker can manipulate the database table prefix parameter to inject malicious PHP code.

This injection allows the attacker to write a PHP shell file on the server, which can then be used to execute arbitrary system commands remotely via a specially crafted POST request. The vulnerability requires no privileges, user interaction, or authentication and can be exploited over the network.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

[{'type': 'paragraph', 'content': 'This vulnerability can be detected by monitoring for unusual POST requests to the installation endpoint (/install) that include manipulation of the database table prefix parameter with injected PHP code.'}, {'type': 'paragraph', 'content': 'Specifically, detection involves looking for POST requests containing suspicious payloads that attempt to write PHP shell code via the db_table_prefix parameter.'}, {'type': 'paragraph', 'content': 'One approach is to inspect web server logs for POST requests to /install with unusual or encoded parameters.'}, {'type': 'paragraph', 'content': 'Example commands to detect such activity might include:'}, {'type': 'list_item', 'content': "Using grep to find suspicious POST requests in Apache logs: grep -i 'POST /install' /var/log/apache2/access.log | grep 'db_table_prefix'"}, {'type': 'list_item', 'content': 'Using network monitoring tools like tcpdump or Wireshark to capture HTTP POST requests to the installation endpoint and analyze payloads for PHP code injection patterns.'}, {'type': 'list_item', 'content': "Searching for newly created or modified PHP files in the web root that could be malicious shells: find /var/www/html -name '*.php' -mtime -7"}, {'type': 'paragraph', 'content': "Automated detection can also be implemented by scanning for the presence of PHP files containing the injected code pattern that checks for the POST parameter 'ccc' and executes system commands."}] [2, 3]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include:

  • Avoid using vulnerable versions of Chevereto Core (3.13.4 and earlier) and upgrade to a fixed version if available.
  • Restrict access to the installation endpoint (/install) to trusted administrators only, or disable it after installation.
  • Implement web application firewall (WAF) rules to block POST requests containing suspicious payloads targeting the db_table_prefix parameter.
  • Harden PHP execution permissions in upload directories and restrict HTTP methods to GET where possible, as done in later Chevereto releases.
  • Monitor logs for suspicious activity and remove any unauthorized PHP shell files found on the server.

These steps help prevent exploitation by limiting the attack surface and blocking malicious payloads.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart