CVE-2023-42245
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 · uneditedSelesta Visual Access Manager < 4.42.2 is vulnerable to Cross Site Scripting (XSS) via monitor/s_scheduledfile.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 confidenceSelesta Visual Access Manager versions prior to 4.42.2 contain a reflected Cross Site Scripting (XSS) vulnerability in the monitor/s_scheduledfile.php script. An attacker can inject malicious JavaScript code through unsanitized user input, which executes in the victim's browser when the crafted payload is processed by the vulnerable PHP endpoint.
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< 4.42.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Selesta Visual Access Manager installationLocate the application installation directory or check web server document root for Selesta Visual Access Manager files. Look for PHP files, configuration files, or the main application entry point that identifies the product.Affected if The product Selesta Visual Access Manager is found in the environment
-
Determine installed versionCheck version files, configuration files, or the main PHP application for a version identifier. Common locations include version.php, config.php, or a README file within the application directory. Compare the found version to 4.42.2.Affected if The installed version is lower than 4.42.2 (e.g., 4.40.0, 4.41.0, etc.)
-
Locate vulnerable scriptSearch for the file monitor/s_scheduledfile.php within the application web directory. This is the PHP endpoint identified as containing the XSS vulnerability.Affected if The file monitor/s_scheduledfile.php exists in the application
-
Verify script accessibilityCheck if the monitor directory and s_scheduledfile.php script are accessible via the web server (HTTP/HTTPS). Attempt to access the URL path /monitor/s_scheduledfile.php to confirm it responds.Affected if The script is accessible over the network and responds to HTTP requests
The environment is affected if Selesta Visual Access Manager is installed with a version lower than 4.42.2 and the monitor/s_scheduledfile.php script is accessible via the web server.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.42.2
Apply vendor patch by upgrading to Selesta Visual Access Manager version 4.42.2 or later. Alternatively, implement input validation and output encoding on the affected PHP script to neutralize XSS vectors.
4.42.2
- Upgrade Selesta Visual Access Manager to version 4.42.2 or later to resolve the XSS vulnerability in monitor/s_scheduledfile.php
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-42245 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-42245 in production — separate from our analysis above.
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.
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.
- 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