CVE-2023-5986
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 · uneditedA CWE-601 URL Redirection to Untrusted Site vulnerability exists that could cause an openredirect vulnerability leading to a cross site scripting attack. By providing a URL-encoded input attackers can cause the software’s web application to redirect to the chosen domain after a successful login is performed.
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 confidenceA CWE-601 open redirect vulnerability exists where URL-encoded user input is not properly validated before being used in a redirect response after successful login. Attackers can craft malicious URLs to redirect authenticated users to attacker-controlled domains, potentially enabling phishing or XSS attacks.
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= 2020= 2021CVSS 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 the installed EcoStruxure Power Monitoring Expert versionCheck the product version through the application interface (typically found in Help > About) or by examining the installation directory for version metadata filesAffected if The installed version is 2020 or 2021 specifically (exact match)
-
Verify the web application component is accessibleConfirm the EcoStruxure Power Monitoring Expert web interface is accessible by accessing the login page via HTTP/HTTPSAffected if The web application is running and accessible to users
-
Identify redirect-capable endpoints after authenticationAfter logging in, observe URL parameters or form submissions that handle post-login redirects (common parameter names include 'redirect', 'url', 'next', 'destination', or similar)Affected if The application uses redirect parameters after successful authentication without strict domain validation
-
Test for open redirect vulnerabilityCraft a test URL with a redirect parameter pointing to an external domain (e.g., redirect parameter set to 'https://evil.example.com') and observe if the application permits the redirect without blocking or rewriting itAffected if The application allows redirection to arbitrary external domains when a redirect parameter is supplied
-
Check for URL-encoded input handling in redirectsReview application logs or use a proxy to inspect how URL-encoded characters in redirect parameters are processed after loginAffected if URL-encoded user input in redirect parameters is not validated against an allowlist of permitted domains
The environment is affected if EcoStruxure Power Monitoring Expert version 2020 or 2021 is installed AND the web-based redirect functionality after login is accessible and does not validate redirect targets against a trusted domain allowlist.
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 dataImplement strict input validation on redirect parameters using an allowlist of permitted domains or verify that the redirect target stays within the application's trusted domain before performing the redirect.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-5986 — 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-5986 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