CVE-2025-57516
BaseFortify
Publication date: 2025-09-29
Last updated on: 2025-10-28
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| publiccms | publiccms | 5.202506.b |
| publiccms | publiccms | 5.202506.a |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-78 | The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an OS command injection in PublicCMS versions V5.202506.a and V5.202506.b. It occurs because the system executes a backup script (backupDB.bat) using database credentials (DATABASE, USERNAME, PASSWORD) without properly sanitizing these inputs. Attackers can craft these credentials with command separators (like |, ;, &) to inject and execute arbitrary commands on the server when the backup script runs. [1]
How can this vulnerability impact me? :
This vulnerability allows attackers to execute arbitrary operating system commands on the server hosting PublicCMS. This can lead to unauthorized actions such as running malicious programs, accessing sensitive data, or compromising the server's integrity and availability. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking if the backupDB.bat script is executed with unsanitized database credentials containing command separators such as ;, &, or |. One practical detection method is to create or inspect database credentials (DATABASE, USERNAME, PASSWORD) for the presence of these characters. You can also attempt to trigger the backup script execution via the backend interface at http://127.0.0.1:8084/admin/sysSite/execScript?navTabId=sysSite/script by selecting backupDB.bat and observing if arbitrary commands appended to credentials are executed. Additionally, inspecting the database.properties file for command separators in jdbc.username or related fields can help detect the vulnerability. Specific commands are not provided, but testing with crafted credentials containing command separators and monitoring the system behavior is recommended. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include sanitizing or restricting the use of command separator characters such as semicolon (;), ampersand (&), and pipe (|) in database names, usernames, and passwords used by the system. Avoid using credentials that contain these characters. Additionally, avoid executing the backupDB.bat script with untrusted input until a proper fix or patch is applied. Reviewing and modifying the backup scripts to properly validate and sanitize input parameters before execution is also recommended. [1]