What is CVE-2026-86217?

CVE-2026-86217 is code-projects Hotel and Tourism Reservation in PHP Database Backup hotel_db%20(1).sql information disclosure. The supplied enrichment data classifies it as Info Disclosure mapped to CWE-200 Exposure of Sensitive Information; CWE-284 Improper Access Control.

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-86217. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-86217 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-86217. 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 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-86217 using CVSS 5.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.

mediumInfo Disclosure

CVE-2026-86217

CVE-2026-86217 — code-projects Hotel and Tourism Reservation in PHP Database Backup hotel_db%20(1).sql information disclosure

A vulnerability was detected in code-projects Hotel and Tourism Reservation in PHP 1.0. Affected is an unknown function of the file /ht/hotel_db%20(1).sql of the component Database Backup Handler. The manipulation results in information disclosure. The attack may be launched remotely. The exploit is now public and may be used.

Published Sep 6, 2026Updated Sep 6, 2026Sources: NVD, code-projects (CNA), GitHub, GitHub Security Advisory, 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

Hotel and Tourism Reservation in PHP

CVSS base

5.3

medium · 6 sources

Remediation

The vendor's own words where we have them.

Upgrade Hotel and Tourism Reservation in PHP 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	Hotel and Tourism Reservation in PHP	1.0	Vulnerable

Attack characteristics

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

Availability

None

Confidentiality

Low

Integrity

None

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

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
5.3	CVSS 3.1	medium	3.9	1.4	NVD, GHSA
5	CVSS 2.0	medium	10	2.9	vuldb.com (CNA)
6.9	CVSS 4.0	medium	—	—	code-projects (CNA)
5.3	CVSS 3.1	medium	—	—	code-projects (CNA)
5.3	CVSS 3.0	medium	—	—	code-projects (CNA)
5	CVSS 2.0	medium	—	—	code-projects (CNA)

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

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-284 · Improper Access Control

Varies by Context::

Mitigation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.

CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor

Read Application Data::

Mitigation: Compartmentalize the system to have safe areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.::

Weakness & attack patterns

CWE-200Exposure of Sensitive Information
CWE-284Improper Access Control

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

CAPEC-116 · ExcavationCAPEC-285 · ICMP Echo Request PingCAPEC-287 · TCP SYN ScanCAPEC-13 · Subverting Environment Variable ValuesCAPEC-302 · TCP FIN ScanCAPEC-303 · TCP Xmas ScanCAPEC-169 · FootprintingCAPEC-304 · TCP Null ScanCAPEC-318 · IP 'ID' Echoed Byte-Order ProbeCAPEC-319 · IP (DF) 'Don't Fragment Bit' Echoing ProbeCAPEC-328 · TCP 'RST' Flag Checksum ProbeCAPEC-326 · TCP Initial Window Size Probe

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 /ht/hotel_db%20(1).sql.
Prioritize edge telemetry for network-reachable Hotel and Tourism Reservation in PHP.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

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 5.3 (AV:N)
Sep 6, 2026 · NVD
Initial · CVE published
Sep 6, 2026 · NVD
Added · GHSA-4f66-847v-p2c5 published (medium)
Sep 6, 2026 · GitHub Security Advisory
CVE published by MITRE.
Sep 6, 2026 · SOCRadar CTI
Reported · Advisory disclosed
Sep 5, 2026 · code-projects
Reported · VulDB entry created
Sep 5, 2026 · code-projects
Reported · VulDB entry last update
Sep 5, 2026 · code-projects

References

8 on the record

code-projects.org/
Vendor Advisory
github.com/ahmadmarz10-hub/CVEsMarz/blob/main/Hotel%20and%20Tourism%20Reservation%20System%20%E2%80%93%20Sensitive%20Information%20Disclosure%20via%20Exposed%20SQL%20Database%20File.md
Exploit, Third Party Advisory
vuldb.com/cve/CVE-2026-86217
Vendor Advisory
vuldb.com/submit/897301
Vendor Advisory
vuldb.com/vuln/399355
Vendor Advisory
vuldb.com/vuln/399355/cti
Vendor Advisory
nvd.nist.gov/vuln/detail/CVE-2026-86217
NVD
github.com/advisories/GHSA-4f66-847v-p2c5
Exploit, Third Party Advisory

Coverage

1 story from the feeds we poll

CVE-2026-86217
vuldb.com · Sep 5, 2026

Elsewhere on this site

code-projectsevery CVE for this vendor
Info Disclosuresame class
CWE-200other 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-86217 is code-projects Hotel and Tourism Reservation in PHP Database Backup hotel_db%20(1).sql information disclosure, a medium vulnerability affecting Hotel and Tourism Reservation in PHP 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-86217. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-86217. 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 5.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.