CVE-2016-4058
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 · uneditedCross-site scripting (XSS) vulnerability in Huawei Policy Center before V100R003C10SPC020 allows remote authenticated users to inject arbitrary web script or HTML via vectors related to "special characters on pages."
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 confidenceAuthenticated cross-site scripting (XSS) vulnerability in Huawei Policy Center versions prior to V100R003C10SPC020 allows remote attackers with valid credentials to inject arbitrary JavaScript or HTML through insufficient sanitization of special characters on web pages.
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= v100r003c00= v100r003c10CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/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 Huawei Policy Center installationCheck for Huawei Policy Center web interface by accessing the admin console through the browser or checking for running services on common ports (typically 8443, 443, or 8080). Look for 'Huawei Policy Center' or 'HPC' branding in the login page.Affected if The Huawei Policy Center web interface is accessible and displays Huawei branding.
-
Determine installed versionLog into the Huawei Policy Center admin console and navigate to the 'About' or 'System Information' page typically found under Settings, Administration, or Help menus. Alternatively, check the version string in the login page footer or in the application's banner/header.Affected if The version displayed is v100r003c00, v100r003c10, or any version prior to V100R003C10SPC020.
-
Check if authentication is enabledVerify that the web interface requires login credentials by attempting to access the console without credentials. Confirm that a login page is presented requiring username and password.Affected if The web interface is accessible and accepts authentication credentials.
-
Identify web pages handling user inputNavigate through the Policy Center console and identify pages that accept user-supplied content such as policy names, descriptions, user profiles, or configuration fields. Look for forms, input fields, or text areas where special characters could be entered.Affected if The console contains pages with input fields that accept user-provided text content.
If Huawei Policy Center is running and the installed version is v100r003c00, v100r003c10, or any version prior to V100R003C10SPC020, and the web interface with user authentication is accessible, the environment is affected by this XSS vulnerability.
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 dataUpgrade Huawei Policy Center to version V100R003C10SPC020 or later. Until patched, restrict access to trusted authenticated users only and implement input validation on all user-supplied content.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-4058 — 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-2016-4058 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