InjectionWeakness · CWE-74

CVE-2026-13552

HIGH · 7.3 CVSS v3.1 Published 2026-06-29

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

82/100

Remediation priority · High

Remotely reachable No privileges Zero-click 7 weeks old

Official description

NVD · unedited

A vulnerability was detected in itsourcecode Online Hotel Management System 1.0. This impacts an unknown function of the file /admin/mod_amenities/controller.php?action=edit. Performing a manipulation of the argument amen_id results in sql injection. It is possible to initiate the attack remotely. The exploit is now public and may be used.

Technical summary

dbcve analysis · moderate confidence

SQL injection vulnerability in itsourcecode Online Hotel Management System 1.0 allows remote attackers to inject malicious SQL commands via the amen_id parameter in the /admin/mod_amenities/controller.php file when performing an edit action.

MitigationReplace dynamic SQL queries with parameterized queries (prepared statements) for the amen_id parameter and all user-supplied inputs in the affected controller to prevent SQL injection.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Confirm the application is itsourcecode Online Hotel Management System

Inspect the application's branding, title pages, or footer for 'itsourcecode Online Hotel Management System' text. Check the server document root for PHP files referencing this product name.

Affected if The application installed is itsourcecode Online Hotel Management System version 1.0 or another version without CVE fixes.
Verify the affected controller file exists

Locate the file /admin/mod_amenities/controller.php within the web server document root. This is typically found under the /admin/ directory of the application installation.

Affected if The file /admin/mod_amenities/controller.php exists and is accessible on the server.
Check if the edit action processes the amen_id parameter

Open /admin/mod_amenities/controller.php and search for code handling the 'amen_id' parameter, particularly within functions or code blocks related to 'edit' or 'update' operations. Look for dynamic SQL query construction using this parameter.

Affected if The controller.php file contains code that processes the amen_id parameter in an edit action without using parameterized queries.
Determine if the /admin/ area is accessible

Attempt to access or verify the accessibility of the /admin/mod_amenities/ path via HTTP/HTTPS from a network perspective. Check if authentication is required or if the admin panel is publicly accessible.

Affected if The admin interface is accessible over the network, allowing the SQL injection attack surface to be reached.
Identify the installed version precisely

Check for a version file, readme.txt, or any file containing version metadata within the application root. Compare the version number to 1.0.

Affected if The installed version is 1.0 or earlier, matching the affected version range.

The environment is affected if itsourcecode Online Hotel Management System version 1.0 is installed, the /admin/mod_amenities/controller.php file exists with vulnerable SQL handling for the amen_id parameter, and the admin interface is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Replace dynamic SQL queries with parameterized queries (prepared statements) for the amen_id parameter and all user-supplied inputs in the affected controller to prevent SQL injection.

Have this fixed Scoped from the published advisory

Consultation3.0 h
Implementation4.0 h
Testing2.0 h
Review / QA1.0 h

10.0 hours of engineering $1,800

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-13552 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-13552 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-13552?

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.

What this is

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.

What belongs here

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

At a glance

A fix existsA vendor remedy is published

Severity 7.3 High

Exploit likelihood EPSS, next 30 days 0.3%

Remediation

A high-priority fix

Have this fixed 10 hrs · Moderate

Typical engagement from $1,800

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-13552 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References