# CVE-2026-132611: SourceCodester Simple Form Builder Web App Forms.php save_response 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:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-gvw6-82vj-cf5r

## What is CVE-2026-132611?

CVE-2026-132611 is a medium-severity vulnerability in SourceCodester Simple Form Builder Web App, published on 19 Nov 2026. 

### Official description

A security vulnerability has been detected in SourceCodester Simple Form Builder Web App 1.0. This impacts the function save_response of the file /classes/Forms.php. The manipulation of the argument q[<index>] leads to unrestricted upload. Remote exploitation of the attack is possible. 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-132611?

It affects 1 product.


Products: Sourcecodester Simple Form Builder Web App.

CPE match criteria (CPE 2.3):

- `cpe:2.3:a:sourcecodester:simple_form_builder_web_app:*:*:*:*:*:*:*:*` from 1.0 up to 1.0

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

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

## Is CVE-2026-132611 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-132611 is a medium-severity vulnerability in SourceCodester Simple Form Builder Web App, published on 19 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-132611 in the wild and no public exploit code.

Affected product: SourceCodester Simple Form Builder Web App. 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-132611/ (Markdown: https://insights.sbomify.com/CVE-2026-132611/index.md)
```

## Sources

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

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