CVE-2019-6020
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 · uneditedOpen redirect vulnerability in PowerCMS 5.12 and earlier (PowerCMS 5.x), 4.42 and earlier (PowerCMS 4.x), and 3.293 and earlier (PowerCMS 3.x) allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a specially crafted URL.
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 confidencePowerCMS contains an open redirect vulnerability in versions 5.12 and earlier, 4.42 and earlier, and 3.293 and earlier. The vulnerability allows remote attackers to craft malicious URLs containing arbitrary redirect targets, enabling phishing attacks by tricking users into visiting attacker-controlled websites.
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.01, <= 3.293>= 4.0, <= 4.42>= 5.0, <= 5.12CVSS 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 PowerCMS installation versionAccess the PowerCMS admin dashboard and locate the version information, typically found in the Help, About, or System Settings section. Alternatively, check for a version file in the installation root directory.Affected if The installed version falls within 3.01 to 3.293, 4.0 to 4.42, or 5.0 to 5.12
-
Compare version against affected rangesIf version is accessible via admin panel or configuration file, verify whether it matches any of the three vulnerable ranges: 3.01 through 3.293, 4.0 through 4.42, or 5.0 through 5.12.Affected if The detected version is equal to or less than 3.293, 4.42, or 5.12 respectively, and greater than or equal to the lower bounds of those ranges
-
Inspect URL redirect behaviorTest the PowerCMS installation by crafting a URL with a redirect parameter (such as ?return_url= or similar) pointing to an external domain. Observe whether the application permits arbitrary external redirects.Affected if The application allows redirection to arbitrary external URLs without proper validation or restriction
A user is affected if their PowerCMS installation version is within 3.01-3.293, 4.0-4.42, or 5.0-5.12 and the application permits unvalidated external URL redirects.
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 to the latest patched version of PowerCMS provided by the vendor. Users should be cautious of clicking untrusted links pointing to PowerCMS installations.
- 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-2019-6020 — 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-2019-6020 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