What is CVE-2026-86518?

CVE-2026-86518 is code-projects Student Crud Operation edit.php sql injection. The supplied enrichment data classifies it as Injection mapped to CWE-89 SQL Injection; CWE-74 Injection.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-86518. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-86518 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

A public PoC is not confirmed from current sources for CVE-2026-86518. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, database audit logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-86518 using CVSS 6.3, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

mediumInjection

CVE-2026-86518

CVE-2026-86518 — code-projects Student Crud Operation edit.php sql injection

A vulnerability has been found in code-projects Student Crud Operation 1.0. This affects an unknown function of the file /edit.php. The manipulation of the argument ID leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

Published Sep 8, 2026Updated Sep 8, 2026Sources: NVD, code-projects (CNA), GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

ahead of 0% of scored CVEs

Affects

code-projects

Student Crud Operation

CVSS base

6.3

medium · 6 sources

Remediation

The vendor's own words where we have them.

Upgrade Student Crud Operation to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
code-projects	Student Crud Operation	1.0	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

Low

Confidentiality

Low

Integrity

Low

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

Low

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
6.3	CVSS 3.1	medium	2.8	3.4	NVD
6.5	CVSS 2.0	medium	8	6.4	vuldb.com (CNA)
5.3	CVSS 4.0	medium	—	—	code-projects (CNA)
6.3	CVSS 3.1	medium	—	—	code-projects (CNA)
6.3	CVSS 3.0	medium	—	—	code-projects (CNA)
6.5	CVSS 2.0	medium	—	—	code-projects (CNA)

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

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Read Application Data
Bypass Protection Mechanism
Modify Application Data

Mitigation: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using persistence layers such as Hibernate or Enterprise Java Beans, which can provide significant protection against SQL injection if used properly.

CWE-74 · Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

Read Application Data
Bypass Protection Mechanism
Alter Execution Logic
Other

Mitigation: Programming languages and supporting technologies might be chosen which are not subject to these issues.

Weakness & attack patterns

CWE-89SQL Injection
CWE-74Injection

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-470 · Expanding Control over the Operating System from the DatabaseCAPEC-109 · Object Relational Mapping InjectionCAPEC-110 · SQL Injection through SOAP Parameter TamperingCAPEC-7 · Blind SQL InjectionCAPEC-108 · Command Line Execution through SQL InjectionCAPEC-66 · SQL Injection

T1562.003Impair Defenses: Impair Command History Logging
T1574.006Hijack Execution Flow: Dynamic Linker Hijacking
T1574.007Hijack Execution Flow: Path Interception by PATH Environment Variable

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Search application, proxy, and WAF logs for requests touching /edit.php.
Prioritize edge telemetry for network-reachable Student Crud Operation.

web/proxy/WAF logsapplication logsnetwork IDS/IPSdatabase audit logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 6.3 (AV:N)
Sep 8, 2026 · NVD
Initial · CVE published
Sep 8, 2026 · NVD
CVE published by MITRE.
Sep 8, 2026 · SOCRadar CTI
Reported · Advisory disclosed
Sep 7, 2026 · code-projects
Reported · VulDB entry created
Sep 7, 2026 · code-projects
Reported · VulDB entry last update
Sep 7, 2026 · code-projects

References

6 on the record

code-projects.org/
Vendor Advisory
github.com/ahmadmarz10-hub/CVEsMarz/blob/main/Student%20CRUD%20Operation%20in%20PHP%20%E2%80%93%20Time-Based%20Blind%20SQL%20Injection%20in%20%60edit.php%60%20via%20%60id%60%20Parameter.md
Exploit, Third Party Advisory
vuldb.com/cve/CVE-2026-86518
Vendor Advisory
vuldb.com/submit/908878
Vendor Advisory
vuldb.com/vuln/399672
Vendor Advisory
vuldb.com/vuln/399672/cti
Vendor Advisory

Coverage

1 story from the feeds we poll

CVE-2026-86518
vuldb.com · Sep 7, 2026

Elsewhere on this site

code-projectsevery CVE for this vendor
Injectionsame class
CWE-89other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-86518 is code-projects Student Crud Operation edit.php sql injection, a medium vulnerability affecting Student Crud Operation from code-projects. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-86518. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-86518. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 6.3 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.