CVE-2026-4970
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 security flaw has been discovered in code-projects Social Networking Site 1.0. This affects an unknown function of the file delete_photos.php of the component Endpoint. The manipulation of the argument ID results in sql injection. The attack can be executed remotely. The exploit has been released to the public and may be used for attacks.
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 confidenceA SQL injection vulnerability exists in the delete_photos.php endpoint of code-projects Social Networking Site 1.0. The ID parameter is not properly sanitized before being used in SQL queries, allowing attackers to inject malicious SQL code. The vulnerability is remotely exploitable and public exploits are available.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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.
-
Confirm the installed product and versionIdentify if the application 'code-projects Social Networking Site' version 1.0 is deployed in your environment. Check your web server document root for the application files and review any version indicators such as a README file, version metadata, or admin panel information.Affected if The application is code-projects Social Networking Site version 1.0 or if the version cannot be determined but the product matches.
-
Locate the vulnerable scriptSearch your web server directories for the file delete_photos.php. Common paths may include /admin/, /php/, or the application root directory.Affected if The file delete_photos.php exists in your deployment.
-
Verify the ID parameter handlingExamine the delete_photos.php source code and locate where the ID parameter is used in SQL queries. Look for direct concatenation of the ID parameter into SQL statements without sanitization, parameter binding, or use of prepared statements.Affected if The ID parameter is used directly in SQL queries without proper sanitization, parameterized queries, or prepared statements.
-
Check if the endpoint is accessibleDetermine if the delete_photos.php endpoint is exposed via the web server. Check your web server configuration and routing to see if this PHP file can be accessed remotely.Affected if The delete_photos.php endpoint is accessible over HTTP/HTTPS without authentication or with weak authentication.
You are affected if you are running code-projects Social Networking Site version 1.0 with the delete_photos.php file present and the ID parameter is used in SQL queries without sanitization or prepared statements.
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 dataImplement parameterized queries or prepared statements for all database operations involving user input. Apply input validation on the ID parameter and sanitize all user-supplied data before database queries. If a vendor patch is available, apply it immediately.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4970 — 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-2026-4970 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