# CVE-2026-122047: Campcodes Complete Advance Loan Management System banner.php move_uploaded_file unrestricted upload


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-j4xp-qrwf-rvjp

## What is CVE-2026-122047?

CVE-2026-122047 is a medium-severity vulnerability in Campcodes Complete Advance Loan Management System, published on 4 Nov 2026. 

### Official description

A security vulnerability has been detected in Campcodes Complete Advance Loan Management System 1.0. This affects the function move_uploaded_file of the file /loan/application/banner.php. Such manipulation of the argument image leads to unrestricted upload. The attack may be launched remotely. The exploit has been disclosed publicly and may be used.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-122047 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-122047 is a medium-severity vulnerability in Campcodes Complete Advance Loan Management System, published on 4 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-122047 exists.

Affected product: Campcodes Complete Advance Loan Management System. 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-122047/ (Markdown: https://insights.sbomify.com/CVE-2026-122047/index.md)
```

## Sources

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

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