dbcve.org
Visual Access ManagerApplication · Seling

CVE-2023-42244

HIGH · 8.8 CVSS v3.1 Published 2025-01-13
Fix available
A fix is available. Upgrade to 4.42.2 or later.
See remediation →
94/100
Remediation priority · Urgent
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
An issue was discovered in Selesta Visual Access Manager (VAM) prior to 4.42.2. An authenticated attacker can perform SQL Injection in multiple POST parameters of /vam/vam_visits.php.

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

An authenticated SQL injection vulnerability exists in Selesta Visual Access Manager (VAM) prior to version 4.42.2. The flaw is located in the vam_visits.php file and affects multiple POST parameters, allowing authenticated attackers to inject malicious SQL queries and potentially exfiltrate or manipulate database contents.

MitigationUpgrade to VAM version 4.42.2 or later which contains the vendor patch. As a temporary mitigation, restrict access to the vulnerable endpoint to only trusted IP addresses and monitor for suspicious SQL-like patterns in POST requests.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 installed VAM version
    Locate the Selesta Visual Access Manager version indicator in the application admin panel, startup banner, or version file (commonly found in /about, /info, or a config/version file). Compare the displayed version number to the affected range of versions prior to 4.42.2.
    Affected if The installed version is lower than 4.42.2
  2. Locate the vulnerable vam_visits.php file
    Search the webroot or application directory for the file vam_visits.php. This file is the location of the SQL injection vulnerability. Check the file existence and its last modification date.
    Affected if The vam_visits.php file exists in the application directory and the VAM version is below 4.42.2
  3. Verify POST parameter acceptance at vulnerable endpoint
    Review the web server logs or use a local proxy to confirm that POST requests are accepted at the vam_visits.php endpoint. The vulnerability exploits POST parameters, not GET parameters.
    Affected if The endpoint accepts POST requests and the application version is < 4.42.2
  4. Check authentication status for VAM application
    Determine whether user authentication is enabled and functional for the VAM application. The SQL injection requires an authenticated session to exploit.
    Affected if User authentication is enabled and you have valid credentials, and the VAM version is < 4.42.2

You are affected if your installed Selesta Visual Access Manager version is prior to 4.42.2, the vam_visits.php file is present, and the application accepts authenticated POST requests to that endpoint.

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 VAM version 4.42.2 or later which contains the vendor patch. As a temporary mitigation, restrict access to the vulnerable endpoint to only trusted IP addresses and monitor for suspicious SQL-like patterns in POST requests.

Recommended fix High confidence

Visual Access Manager 4.42.2

  1. Verify current installed version of Visual Access Manager (VAM) by checking the application or consulting system documentation
  2. Plan and schedule the upgrade during a maintenance window
  3. Download Visual Access Manager version 4.42.2 or later from the vendor's official distribution channel (gitlab.com or vendor support)
  4. Back up the current installation including database and configuration files
  5. Upgrade the Visual Access Manager installation to version 4.42.2 following vendor upgrade documentation
  6. Verify the upgrade was successful by checking the version number
  7. Test that the application functions correctly, particularly the /vam/vam_visits.php functionality
  8. Validate that the SQL injection vulnerability is no longer present
Caveat Review vendor release notes for any breaking changes between current version and 4.42.2

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

Fix this in Visual Access Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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