CVE-2022-30777
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 · uneditedParallels H-Sphere 3.6.1713 allows XSS via the index_en.php from parameter.
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 confidenceReflected Cross-Site Scripting (XSS) vulnerability in Parallels H-Sphere 3.6.1713 where user-supplied input via the 'from' parameter in index_en.php is not properly sanitized before being reflected back in the application's response.
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= 3.6.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.
-
Confirm Parallels H-Sphere installationSearch the web server filesystem for the 'index_en.php' file that is part of H-Sphere web panel, typically located in the web root directory under the hsphere directory or similar installation path.Affected if The file index_en.php from Parallels H-Sphere is found on the system.
-
Verify H-Sphere versionLocate and read the version file or version string within the H-Sphere installation directory. Check the exact version number against the affected version 3.6.2 or build 1713.Affected if The installed version is 3.6.2 or build 1713.
-
Locate the vulnerable index_en.phpAccess the web server document root and confirm the presence of index_en.php in the path where H-Sphere handles English language pages.Affected if The file index_en.php exists in the H-Sphere web directory.
-
Inspect the 'from' parameter handlingExamine the source code of index_en.php and search for code that handles the 'from' GET or POST parameter. Look for cases where this parameter is used in HTTP responses without sanitization functions such as htmlspecialchars or equivalent encoding.Affected if The code takes the 'from' parameter and reflects it directly into the HTML output without proper encoding or validation.
-
Test for reflected XSS manuallySend a request to index_en.php with a crafted 'from' parameter value such as 'from=<script>alert(1)</script>' and examine the response to see if the script tag appears unescaped in the output.Affected if The script tags or other malicious payload are reflected verbatim in the response without HTML encoding.
A system is affected if it runs Parallels H-Sphere version 3.6.2 (or build 1713) with the index_en.php file present and the 'from' parameter is reflected in responses without sanitization.
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.
From vendor dataApply vendor patch or update to latest version; implement input validation and output encoding for the 'from' parameter in index_en.php to neutralize malicious script payloads.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30777 — 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-2022-30777 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