Visual Access ManagerApplication · Seling

CVE-2023-42243

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-13
Fix available
A fix is available. Upgrade to 4.42.2 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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
In Selesta Visual Access Manager < 4.42.2, an authenticated user can access the administrative page /common/vam_Sql.php, which allows for arbitrary SQL queries.

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 · high confidence

Selesta Visual Access Manager versions before 4.42.2 lack proper authorization controls on the /common/vam_Sql.php endpoint, allowing any authenticated user (even low-privilege users) to access an administrative interface that permits execution of arbitrary SQL queries. This represents a combination of broken access control (CWE-284) and potential SQL injection exposure.

MitigationUpgrade to Selesta Visual Access Manager version 4.42.2 or later. Until patched, restrict network access to the application and monitor logs for suspicious SQL query patterns.

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
Visual Access ManagerApplication
Affected:< 4.42.2

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

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

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 the installed version of Selesta Visual Access Manager
    Locate the application's version file, about page, or check the HTTP response headers/banner. Compare the version number to the affected range of versions before 4.42.2.
    Affected if The installed version is lower than 4.42.2 (e.g., 4.40.0, 4.41.0, 4.42.0).
  2. Verify the vulnerable endpoint exists
    Check if the file /common/vam_Sql.php is present in the web application root directory or accessible via HTTP request.
    Affected if The /common/vam_Sql.php endpoint exists and responds to requests.
  3. Confirm user authentication is enabled
    Check if the application has at least one user account configured and authentication is required to access the application.
    Affected if User authentication is required to access the application and any valid user credentials can be used to reach the vulnerable endpoint.
  4. Check for low-privilege user access
    Attempt to access the application with a low-privilege or non-administrator user account, then navigate to or request the /common/vam_Sql.php endpoint.
    Affected if A low-privilege authenticated user can access the /common/vam_Sql.php administrative interface without elevated permissions.

The environment is affected if Selesta Visual Access Manager version is below 4.42.2 and the /common/vam_Sql.php endpoint is accessible to authenticated users without proper authorization checks.

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 4.42.2 or later
Fixed in 4.42.2
Interim mitigation

Upgrade to Selesta Visual Access Manager version 4.42.2 or later. Until patched, restrict network access to the application and monitor logs for suspicious SQL query patterns.

Recommended fix Moderate confidence

4.42.2

  1. Identify the current installed version of Visual Access Manager
  2. Schedule a maintenance window for the upgrade
  3. Back up the current Visual Access Manager installation and its database
  4. Upgrade Visual Access Manager to version 4.42.2 or later
  5. Verify the upgrade was successful by checking the version number
  6. Confirm the /common/vam_Sql.php endpoint is no longer accessible to non-administrative users or has been properly secured
Caveat Review release notes for 4.42.2 to check for any breaking changes or required migration steps before upgrading in production

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

Fix this in Visual Access Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-42243 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-42243 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