CVE-2026-13553
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 flaw has been found in itsourcecode Online Hotel Management System 1.0. Affected is an unknown function of the file /admin/mod_amenities/controller.php?action=add. Executing a manipulation of the argument image can lead to unrestricted upload. It is possible to launch the attack remotely. The exploit has been published and may be used.
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 confidenceThe itsourcecode Online Hotel Management System 1.0 contains an unrestricted file upload vulnerability in /admin/mod_amenities/controller.php?action=add. The 'image' parameter accepts arbitrary file uploads without proper validation, allowing remote attackers to upload malicious PHP scripts and achieve remote code execution.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify if itsourcecode Online Hotel Management System is installedSearch the web root for characteristic files such as 'index.php', 'admin/index.php', or directories named 'mod_amenities', 'hotel', or 'online_hotel_management'. Check page titles, footers, or meta tags for 'itsourcecode' or 'Online Hotel Management System' branding.Affected if The application is found in the web directory or responds to HTTP requests.
-
Determine the installed versionReview any version files, README files, or meta information in the application root. Check footer content or admin dashboard for version numbers. Compare against version 1.0.Affected if The installed version is 1.0 or cannot be determined (treat as potentially affected).
-
Verify the vulnerable admin endpoint existsAttempt to access or enumerate /admin/mod_amenities/controller.php via HTTP requests or directory listing. Check if the path /admin/mod_amenities/ exists in the web root.Affected if The directory path /admin/mod_amenities/ exists and contains controller.php.
-
Check if the admin interface is accessible without proper authenticationInspect the application's authentication mechanism for /admin/ endpoints. Determine if authentication is enforced or if the addAmenities function (action=add) can be reached without valid admin credentials.Affected if The admin endpoint is accessible without authentication or uses weak/blank credentials.
-
Inspect upload directories for suspicious filesSearch web-accessible directories (commonly /admin/mod_amenities/, /uploads/, /images/, or /assets/) for unexpected .php, .phtml, or .php5 files. Review file modification timestamps for recent uploads.Affected if Executable PHP files exist in upload directories outside of expected template/assets locations.
If the itsourcecode Online Hotel Management System 1.0 is installed and the /admin/mod_amenities/ endpoint is accessible, the environment is likely affected by this unrestricted file upload vulnerability.
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 strict allowlist-based file validation for both MIME type and extension, store uploads outside the web root, rename uploaded files to prevent execution, and enforce proper authentication/authorization checks on the admin endpoint.
- 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-13553 — 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-13553 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