# CVE-2026-118585: configuroweb inventariobasico Add Product addlist.php cross site scripting


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-mq3c-h3gr-228f

## What is CVE-2026-118585?

CVE-2026-118585 is a medium-severity vulnerability in configuroweb inventariobasico, published on 28 Oct 2026. 

### Official description

A vulnerability was identified in configuroweb inventariobasico c9377cdba474deb3eb5a0704d197b5733af16b47/f9db0c0a04d79ad931c218140df4fb23809d4fab. This vulnerability affects unknown code of the file addlist.php of the component Add Product Page. Such manipulation of the argument product name leads to cross site scripting. The attack may be launched remotely. The exploit is publicly available and might be used. This product operates on a rolling release basis, ensuring continuous delivery. Consequently, there are no version details for either affected or updated releases. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-118585?


## How do I fix CVE-2026-118585?

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

## Is CVE-2026-118585 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-118585 and fix it if it is affected.

What it is: CVE-2026-118585 is a medium-severity vulnerability in configuroweb inventariobasico, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-118585 in the wild and no public exploit code.

Affected product: configuroweb inventariobasico. 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-2026-118585/ (Markdown: https://insights.sbomify.com/CVE-2026-118585/index.md)
```

## Sources

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

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