CVE-2025-11334
BaseFortify
Publication date: 2025-10-06
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| campcodes | online_apartment_visitor_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
| 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?
CVE-2025-11334 is a critical SQL injection vulnerability in Campcodes Online Apartment Visitor Management System version 1.0, specifically in the file /visitor-detail.php via the 'editid' parameter. Due to insufficient input validation and sanitization, attackers can inject malicious SQL code remotely without authentication. This allows them to manipulate SQL queries to perform unauthorized database operations such as viewing, modifying, or deleting sensitive data. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to unauthorized access to the database, enabling attackers to view, modify, or delete sensitive information. It can result in data disclosure, data corruption, full system compromise, and potential service disruption. Since the attack can be performed remotely without authentication, it poses a high risk to system security and data integrity. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'editid' parameter in the /visitor-detail.php file for SQL injection. You can use tools like sqlmap to automate detection, for example: sqlmap -u "http://target/visitor-detail.php?editid=1" --batch. Additionally, manual testing with payloads such as 'editid=5' AND 4811=4811 AND 'NWzs'='NWzs' (Boolean-based blind SQLi) or 'editid=5' AND (SELECT SLEEP(5)) AND 'jCYR'='jCYR' (Time-based blind SQLi) can help identify the vulnerability. Also, Google dorking with queries like "inurl:visitor-detail.php" can help identify potentially vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the 'editid' parameter, and minimizing database user privileges by avoiding high-privilege accounts for routine operations. Regular security audits should be conducted to detect and address vulnerabilities promptly. Since no patches are currently reported, replacing the affected product with an alternative solution is recommended to ensure security. [2, 3]