dbcve.org
BookmarkApplication · Mtab

CVE-2023-7193

HIGH · 8.1 CVSS v3.1 Published 2023-12-31
Fix available
A fix is available. Upgrade to after 1.2.6 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability was found in MTab Bookmark up to 1.2.6 and classified as critical. This issue affects some unknown processing of the file public/install.php of the component Installation. The manipulation leads to improper access controls. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-249395. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

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 confidence

The vulnerability exists in the Installation component of MTab Bookmark (versions up to 1.2.6), specifically in the public/install.php file. It allows unauthorized attackers to manipulate installation processes due to improper access controls, potentially enabling unauthorized re-installation or configuration of the application. The public exploit availability and CVSS 8.1 indicate significant risk despite the 'rather high' attack complexity noted.

MitigationRemove or delete the install.php file and entire installation directory from production deployments, or implement proper authentication/authorization controls to block unauthorized access to installation scripts.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
BookmarkApplication
Affected:<= 1.2.6

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 checks

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

  1. Identify if MTab Bookmark is installed
    Look for MTab Bookmark application files in the web root directory. Common locations include directories named 'mtab-bookmark', 'mtbookmark', or check for files containing 'MTab' or 'Bookmark' in the document root.
    Affected if MTab Bookmark software is present on the server
  2. Determine installed version
    Check version file or composer.json in the application directory for the version number. The version may also be displayed in the application footer or a dedicated version info page.
    Affected if Installed version is 1.2.6 or lower (any version up to and including 1.2.6)
  3. Locate the installation script
    Search for the file 'public/install.php' within the MTab Bookmark application directory structure. Use file system search or check the web root for: /path/to/webroot/public/install.php
    Affected if The file public/install.php exists in the deployed application
  4. Verify installation directory accessibility
    Check if the installation directory (public/ or install/) is accessible via HTTP/HTTPS request. Attempt to access the install.php URL directly through a web browser or curl command.
    Affected if The install.php script is accessible over the network without authentication
  5. Check if installation has already been completed
    Inspect the application configuration or database to determine if the application is already installed. Look for config files, database connection files, or an installed status marker.
    Affected if Application is installed but install.php remains accessible and executable

You are affected if MTab Bookmark version 1.2.6 or lower is installed AND the public/install.php file remains accessible on the server, allowing potential unauthorized re-installation.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.2.6
Interim mitigation

Remove or delete the install.php file and entire installation directory from production deployments, or implement proper authentication/authorization controls to block unauthorized access to installation scripts.

Recommended fix Low confidence
  1. After completing the installation, delete or remove the public/install.php file from the web server
  2. Verify that the installation directory is not accessible via HTTP/HTTPS
  3. Ensure proper file permissions are set to prevent unauthorized access to installation scripts

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Bookmark Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-7193 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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