CVE-2025-55444
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 · uneditedA SQL injection vulnerability exists in the id2 parameter of the cancel_booking.php page in Online Artwork and Fine Arts MCA Project 1.0. A remote attacker can inject arbitrary SQL queries, leading to database enumeration and potential remote code execution.
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 · high confidenceSQL injection vulnerability in the id2 parameter of cancel_booking.php in Online Artwork and Fine Arts MCA Project 1.0 allows remote attackers to inject arbitrary SQL queries. The application fails to sanitize user input before incorporating it into SQL statements, enabling database enumeration and potentially remote code execution via SQL injection techniques.
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= 1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if the application is deployedLocate PHP files related to artwork, booking, or fine arts management in your web server directories. Search for files containing 'artwork', 'fine arts', or 'booking' in the filename or content.Affected if The Vishalmathur Online Artwork And Fine Arts Project PHP application is found in your environment
-
Verify the installed versionCheck version files, README files, or any version metadata within the application directory. Compare your installed version against version 1.0.Affected if The installed version is exactly 1.0
-
Locate cancel_booking.phpSearch the application directory for the file cancel_booking.php. This is the vulnerable script containing the SQL injection flaw.Affected if cancel_booking.php exists in the application
-
Inspect the id2 parameter handlingOpen cancel_booking.php and examine how the id2 parameter is processed. Look for SQL query execution that incorporates the id2 parameter directly without parameterized queries, prepared statements, or input sanitization.Affected if The id2 parameter is used directly in SQL statements without sanitization or prepared statements
-
Check web server access logsReview web server access logs for requests to cancel_booking.php with unusual id2 parameter values that may indicate exploitation attempts.Affected if Suspicious requests with SQL injection payloads in the id2 parameter are present in logs
Your environment is affected if you have the Vishalmathur Online Artwork And Fine Arts Project version 1.0 deployed with cancel_booking.php containing unsanitized id2 parameter in SQL queries.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataReplace dynamic SQL queries with parameterized queries (prepared statements) in cancel_booking.php. Additionally, implement input validation, apply the principle of least privilege to database accounts, and consider deploying a WAF as defense-in-depth.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-55444 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-55444 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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