LoginwpWordPress extension · Profilepress
CVE-2016-10925
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 · uneditedThe peters-login-redirect plugin before 2.9.1 for WordPress has XSS during the editing of redirect URLs.
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 confidenceThe peters-login-redirect WordPress plugin before version 2.9.1 contains a stored Cross-Site Scripting (XSS) vulnerability in its redirect URL editing functionality. Attackers can inject malicious JavaScript into redirect URL fields that executes when administrators access the editing interface.
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
LoginwpWordPress extension
< 2.9.1CVSS 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.
-
Verify plugin installationNavigate to WordPress admin dashboard > Plugins and locate 'peters-login-redirect' or 'Loginwp' in the installed plugins list. Confirm the plugin is active.Affected if The plugin is installed and active in WordPress
-
Check installed versionIn the Plugins list, find the plugin and view its version information. Compare this version number against the affected range (versions before 2.9.1).Affected if The installed version is below 2.9.1
-
Access redirect URL settingsNavigate to the plugin settings page where redirect URLs are configured (typically under Settings > Login Redirect or similar) and locate the redirect URL configuration fields.Affected if The redirect URL editing functionality is accessible and configured
-
Inspect redirect URL fieldsExamine all redirect URL fields in the plugin configuration for any unexpected or suspicious URL values, including those containing JavaScript: or other script-related patterns.Affected if Redirect URL fields contain unexpected or potentially malicious values, especially those with script tags or javascript: prefixes
The environment is affected if the peters-login-redirect/Profilepress Loginwp plugin version is below 2.9.1 and the redirect URL editing functionality is accessible and configured.
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 data2.9.1
Update the peters-login-redirect plugin to version 2.9.1 or later to remediate the XSS vulnerability in the redirect URL editing functionality.
Fix this in Loginwp
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-2016-10925 — 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-10925 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