# CVE-2018-14931: Open redirect in n/a

> An open redirect vulnerability in Polaris FT Intellect Core Banking allows attackers to redirect users to malicious sites via a crafted URI.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Apr 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8r54-hq49-gq6m

## What is CVE-2018-14931?

CVE-2018-14931 is a medium-severity vulnerability in n/a, published on 30 Apr 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An issue was discovered in the Core and Portal modules in Polaris FT Intellect Core Banking 9.7.1. An open redirect exists via a /IntellectMain.jsp?IntellectSystem= URI.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2018-14931?

It affects 1 product.


Products: Polarisft Intellect Core Banking.

## How do I fix CVE-2018-14931?

No fix has been published for CVE-2018-14931 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-14931 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-14931 exists.

Public exploit code:

- Polarisft Intellect Core Banking Software Version 9.7.1 - Open Redirect (nuclei): http/cves/2018/CVE-2018-14931.yaml

## Other vulnerabilities in n/a

- [CVE-2018-14874](https://insights.sbomify.com/CVE-2018-14874/): SQL injection in n/a (high 8.8)
- [CVE-2018-14930](https://insights.sbomify.com/CVE-2018-14930/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-14875](https://insights.sbomify.com/CVE-2018-14875/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-14931 and fix it if it is affected.

What it is: CVE-2018-14931 is a medium-severity vulnerability in n/a, published on 30 Apr 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-14931 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-14931/ (Markdown: https://insights.sbomify.com/CVE-2018-14931/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-14931
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-14931
- OSV: https://osv.dev/vulnerability/CVE-2018-14931

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-14931/
Summaries are generated and may contain mistakes; the official description above is the record.