dbcve.org
Visual Access ManagerApplication · Seling

CVE-2023-42246

MEDIUM · 6.1 CVSS v3.1 Published 2025-01-13
Fix available
A fix is available. Upgrade to 4.42.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Selesta Visual Access Manager < 4.42.2 is vulnerable to Cross Site Scripting (XSS) via /vam/vam_ep.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

Selesta Visual Access Manager versions before 4.42.2 contain a stored Cross-Site Scripting (XSS) vulnerability in the /vam/vam_ep.php endpoint. Attackers can inject malicious JavaScript code that executes in the browsers of other users who access the affected functionality.

MitigationUpgrade to version 4.42.2 or later. Alternatively, implement proper input validation and output encoding on the vam_ep.php endpoint to sanitize user-supplied data before rendering.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 Selesta Visual Access Manager installation
    Search the system for files or directories named 'vam' or check web server document roots for the '/vam/' path. Look for the Visual Access Manager application directory structure.
    Affected if The Visual Access Manager application is present on the system.
  2. Locate the vulnerable endpoint file
    Check for the existence of the file 'vam_ep.php' within the /vam/ directory. This is typically found at /vam/vam_ep.php relative to the web application root.
    Affected if The file vam_ep.php exists in the vam directory.
  3. Determine installed version
    Check version information in application files, configuration files, or the product itself. Look for version strings in the vam directory or access the application's about/info page if available. Compare against the affected range: versions before 4.42.2 are vulnerable.
    Affected if The installed version is below 4.42.2.
  4. Verify endpoint accessibility
    Confirm the vam_ep.php endpoint is accessible via HTTP/HTTPS on the web server. Test by accessing the URL in a browser or using a curl request to see if the endpoint responds.
    Affected if The endpoint is accessible over the network and responds to requests.

The environment is affected if Selesta Visual Access Manager is installed with a version lower than 4.42.2 and the vam_ep.php endpoint is accessible.

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 version 4.42.2 or later. Alternatively, implement proper input validation and output encoding on the vam_ep.php endpoint to sanitize user-supplied data before rendering.

Recommended fix High confidence

4.42.2

  1. 1. Backup the current Visual Access Manager installation and database before proceeding with any upgrade.
  2. 2. Download Visual Access Manager version 4.42.2 or later from the official vendor source (gitlab.com or vendor support portal).
  3. 3. Review the vendor's upgrade documentation for version 4.42.2.
  4. 4. Deploy the upgrade package to the production environment following vendor-provided instructions.
  5. 5. Verify the upgrade was successful by checking the version number in the application.
  6. 6. Test the /vam/vam_ep.php endpoint to confirm the XSS vulnerability is remediated.
  7. 7. Clear any application caches and session data if applicable.

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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