# CVE-2026-132610: SourceCodester Simple Form Builder Web App Forms.php save_form code injection


- **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-pxff-4qgr-hm63

## What is CVE-2026-132610?

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

### Official description

A security flaw has been discovered in SourceCodester Simple Form Builder Web App 1.0. The impacted element is the function save_form of the file /classes/Forms.php. Performing a manipulation of the argument form_code/form_data results in code injection. The attack may be initiated remotely. The exploit has been released to the public and may be used for attacks.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

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-132610?

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

## Is CVE-2026-132610 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-132610 is a medium-severity vulnerability in SourceCodester Simple Form Builder Web App, published on 19 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-132610 exists.

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

## Sources

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

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