CVE-2017-12138
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 · uneditedXOOPS Core 2.5.8 has a stored URL redirect bypass vulnerability in /modules/profile/index.php because of the URL filter.
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 confidenceXOOPS Core 2.5.8 contains a stored URL redirect bypass vulnerability in the profile module (/modules/profile/index.php). The application's URL filter, intended to prevent open redirects by validating redirect URLs, can be bypassed, allowing attackers to store malicious redirect URLs (e.g., to phishing sites) that will be presented to other users viewing profiles.
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= 2.5.8CVSS 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 XOOPS Core versionLocate the version file in your XOOPS installation (typically in /include/version.php or the main admin panel under System > About). Compare the version number to 2.5.8.Affected if The installed version is exactly 2.5.8
-
Confirm profile module is installedCheck for the existence of the /modules/profile/ directory in your XOOPS root installation. Access the admin panel and verify the profile module is listed as active in Module Administration.Affected if The profile module directory exists and the module is activated in the XOOPS admin panel
-
Inspect profile redirect logicExamine the file /modules/profile/index.php for URL handling code, specifically look for redirect or URL validation functions. Search for code handling the 'redirect' or 'to' parameters.Affected if The file contains redirect logic that accepts user-supplied URLs without strict validation against a trusted domain allowlist
-
Test redirect parameter behaviorIf you have access to a test profile, create or edit a profile field that triggers a redirect (such as a website URL field or any field that generates a redirect URL). Attempt to save a URL to an external domain (e.g., http://attacker.com).Affected if The application allows storing and subsequently redirecting users to an external domain not matching the legitimate site domains
You are affected if running XOOPS Core 2.5.8 with the profile module enabled and the application permits external URLs in redirect functionality.
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 dataApply available patches from XOOPS project to fix URL validation in the profile module; implement strict allowlist-based URL validation and reject any redirect URLs not matching trusted domains.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12138 — 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-2017-12138 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