Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Itsourcecode Event Calendar In PHP v2.3 process.php v2.3 SQL injection #1

Open
AutoZhou1 opened this issue Jun 14, 2024 · 0 comments
Open

Comments

@AutoZhou1
Copy link
Owner

Itsourcecode Event Calendar In PHP v2.3 process.php v2.3 SQL injection

NAME OF AFFECTED PRODUCT(S)

  • Event Calendar In PHP

Vendor Homepage

AFFECTED AND/OR FIXED VERSION(S)

submitter

  • Code099

Vulnerable File

  • process.php

VERSION(S)

  • v2.3

Software Link

PROBLEM TYPE

Vulnerability Type

  • SQL injection

Root Cause

  • A SQL injection vulnerability was found in the 'process.php' file of the 'Event Calendar In PHP' project. The reason for this issue is that attackers inject malicious code from the parameter "userId " and use it directly in SQL queries without appropriate cleaning or validation. This allows attackers to forge input values, thereby manipulating SQL queries and performing unauthorized operations.
1

Impact

  • Attackers only need to use registered regular users to exploit this SQL injection vulnerability for unauthorized database access, sensitive data leakage, data tampering, comprehensive system control, and even service interruption, posing a serious threat to system security and business continuity.

DESCRIPTION

  • Due to insufficient user input validation for the "userId " parameter, a serious SQL injection vulnerability was discovered in the login function of the " Event Calendar In PHP", allowing attackers to inject malicious SQL queries. Therefore, attackers can gain unauthorized access to the database, modify or delete data, and access sensitive information without logging in. Immediate remedial measures are needed to ensure system security and protect data integrity.

Vulnerability details and POC

Vulnerability type:

  • time-based blind
  • boolean-based blind
  • error-based
  • UNION query

Vulnerability location:

  • 'userId ' parameter

Payload:

2

The following are screenshots of some specific information obtained from testing and running with the sqlmap tool:

sqlmap -u "http://192.168.210.199:1220/event-management/api/process.php?cmd=user&userId=16" --batch --dbs
3

Suggested repair

  1. Use prepared statements and parameter binding:
    Preparing statements can prevent SQL injection as they separate SQL code from user input data. When using prepare statements, the value entered by the user is treated as pure data and will not be interpreted as SQL code.

  2. Input validation and filtering:
    Strictly validate and filter user input data to ensure it conforms to the expected format.

  3. Minimize database user permissions:
    Ensure that the account used to connect to the database has the minimum necessary permissions. Avoid using accounts with advanced permissions (such as' root 'or' admin ') for daily operations.

  4. Regular security audits:
    Regularly conduct code and system security audits to promptly identify and fix potential security vulnerabilities.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant