LearnpressWordPress extension · Thimpress
CVE-2018-16174
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 LearnPress prior to version 3.1.0 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via unspecified vectors.
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 confidenceLearnPress plugin versions prior to 3.1.0 contain an open redirect vulnerability that allows remote attackers to craft malicious URLs which redirect authenticated users to arbitrary external websites. This is a classic open redirect flaw where user-supplied input in a redirect parameter is not properly validated, enabling phishing attacks where users believe they are on the legitimate LearnPress site but are actually being redirected to a malicious domain.
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
LearnpressWordPress extension
< 3.1.0CVSS 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.0/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 if LearnPress is installedLocate the LearnPress plugin files in your WordPress installation, typically in wp-content/plugins/learnpress/ directory, or check via WordPress admin plugin listAffected if LearnPress plugin is not found in the installation
-
Determine installed LearnPress versionOpen the main plugin file (usually learnpress.php) and locate the version definition, or check the version displayed in WordPress admin plugin listAffected if Version number cannot be determined or is missing
-
Compare version against vulnerable rangeCompare the installed version number to 3.1.0 using standard version comparisonAffected if Installed version is less than 3.1.0 (e.g., 3.0.x, 2.x, or any version prior to 3.1.0)
-
Verify redirect functionality is accessibleCheck if the LearnPress authentication and redirection features are in use by examining URLs for redirect parameters (such as ?redirect= or similar query parameters used by LearnPress)Affected if LearnPress is actively handling user authentication and processing redirect parameters
A system is affected if LearnPress version is below 3.1.0 and the redirect parameter feature is accessible to authenticated users.
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 data3.1.0
Update LearnPress to version 3.1.0 or later to patch the open redirect vulnerability. Additionally, implement URL validation to ensure redirect destinations are relative or trusted domains.
Fix this in Learnpress
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-16174 — 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-2018-16174 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