# CVE-2017-17926: Information disclosure in n/a

> Predictable registration URLs allow attackers to register with spoofed emails, bypassing validation controls in the Professional Service Script.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-6j6m-2jpp-xcg5

## What is CVE-2017-17926?

CVE-2017-17926 is a medium-severity vulnerability in n/a, published on 26 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PHP Scripts Mall Professional Service Script has a predicable registration URL, which makes it easier for remote attackers to register with an invalid or spoofed e-mail address.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2017-17926?

It affects 1 product.


Products: Ordermanagementscript Professional Service Script.

## How do I fix CVE-2017-17926?

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

## Is CVE-2017-17926 being exploited?

There is no known exploitation of CVE-2017-17926 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2017-17928](https://insights.sbomify.com/CVE-2017-17928/): SQL injection in n/a (critical 9.8)
- [CVE-2017-17930](https://insights.sbomify.com/CVE-2017-17930/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2017-17924](https://insights.sbomify.com/CVE-2017-17924/): Path traversal in n/a (medium 5.3)
- [CVE-2017-17927](https://insights.sbomify.com/CVE-2017-17927/): Path traversal in n/a (medium 5.3)
- [CVE-2017-17925](https://insights.sbomify.com/CVE-2017-17925/): Cross-site scripting in n/a (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-17926 and fix it if it is affected.

What it is: CVE-2017-17926 is a medium-severity vulnerability in n/a, published on 26 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-17926 in the wild and no public exploit code.

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-2017-17926/ (Markdown: https://insights.sbomify.com/CVE-2017-17926/index.md)
```

## Sources

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

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