# CVE-2018-7447: Cross-site scripting in n/a

> Persistent XSS in mojoPortal blog fields allows attackers to inject scripts, though maintainers dispute this as admin-only functionality.

- **Severity:** Medium 4.8 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-fw82-9c96-r36g

## What is CVE-2018-7447?

CVE-2018-7447 is a medium-severity cross-site scripting vulnerability in n/a, published on 24 Feb 2018. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

mojoPortal through 2.6.0.0 is prone to multiple persistent cross-site scripting vulnerabilities because it fails to sanitize user-supplied input. The 'Title' and 'Subtitle' fields of the 'Blog' page are vulnerable. NOTE: The software maintainer disputes this as a vulnerability because the fields claimed to be vulnerable to XSS are only available to administrators who are supposed to have access to add scripts

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Mojoportal Mojoportal.

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

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

## Is CVE-2018-7447 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-44008](https://insights.sbomify.com/CVE-2023-44008/): File upload in n/a (critical 9.8)
- [CVE-2023-44009](https://insights.sbomify.com/CVE-2023-44009/): File upload in n/a (critical 9.8)
- [CVE-2023-44011](https://insights.sbomify.com/CVE-2023-44011/): Code injection in n/a (critical 9.8)
- [CVE-2023-24323](https://insights.sbomify.com/CVE-2023-24323/): XML external entity in n/a (high 8.8)
- [CVE-2022-40341](https://insights.sbomify.com/CVE-2022-40341/): File upload in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-7447 is a medium-severity cross-site scripting vulnerability in n/a, published on 24 Feb 2018. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-7447 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-2018-7447/ (Markdown: https://insights.sbomify.com/CVE-2018-7447/index.md)
```

## Sources

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

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