dbcve.org
Ac Repair And Services SystemApplication · Oretnom23

CVE-2023-3657

CRITICAL · 9.8 CVSS v3.1 Published 2023-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability, which was classified as critical, has been found in SourceCodester AC Repair and Services System 1.0. This issue affects some unknown processing of the file Master.php?f=save_book of the component HTTP POST Request Handler. The manipulation of the argument id leads to sql injection. The attack may be initiated remotely. The associated identifier of this vulnerability is VDB-234011.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

SQL injection vulnerability in SourceCodester AC Repair and Services System 1.0 allows remote attackers to inject arbitrary SQL commands via the 'id' parameter in POST requests to Master.php?f=save_book. The lack of input sanitization or parameterized queries in the HTTP POST Request Handler component enables unauthenticated remote code execution via database manipulation.

MitigationImplement prepared statements/parameterized queries for all database operations involving user input, particularly the 'id' parameter. Apply input validation and output encoding as defense-in-depth measures.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ac Repair And Services SystemApplication
Affected:= 1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed application version
    Locate and examine the application files for version information. Check the source code, README, or any version file in the web root directory that indicates the AC Repair and Services System version.
    Affected if The application version is 1.0 specifically (Oretnom23 Ac Repair And Services System = 1.0)
  2. Verify the vulnerable PHP file exists
    Check if the file Master.php exists in the web application's directory structure, typically in the root or admin directory of the installed AC Repair and Services System.
    Affected if Master.php is present in the application directory
  3. Examine the POST handler for the save_book function
    Locate and inspect the Master.php file, specifically the code handling the 'save_book' function (the ?f=save_book parameter). Look for the POST request handler that processes the 'id' parameter.
    Affected if The code processes POST requests with an 'id' parameter at the save_book function
  4. Check for SQL query handling in the vulnerable component
    Review the database query code within Master.php where the 'id' parameter from POST requests is used. Look for direct string concatenation or lack of prepared statements in SQL queries.
    Affected if The 'id' parameter is directly inserted into SQL queries without parameterized queries or input sanitization

Your environment is affected if you are running SourceCodester AC Repair and Services System version 1.0 and the Master.php file with the save_book function handles the 'id' parameter without prepared statements.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement prepared statements/parameterized queries for all database operations involving user input, particularly the 'id' parameter. Apply input validation and output encoding as defense-in-depth measures.

Recommended fix Low confidence
  1. 1. Locate the file Master.php in the application directory
  2. 2. Find the function save_book that handles the POST request
  3. 3. Identify the SQL query that uses the 'id' parameter without sanitization
  4. 4. Replace dynamic SQL queries with prepared statements (parameterized queries)
  5. 5. Use mysqli_prepare() or PDO::prepare() with bound parameters instead of concatenating user input directly into SQL
  6. 6. Alternatively, implement input validation using filter_var() or intval() to ensure 'id' is numeric before using in queries
  7. 7. Apply the same SQL injection mitigation to all other parameters in the file
  8. 8. Test the fix by attempting SQL injection payloads in the 'id' parameter

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ac Repair And Services System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-3657 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-3657 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data