# CVE-2019-12363: Cross-site request forgery in n/a

> An attacker can force a user to disable two-factor authentication via a forged request, lowering account security.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cp4x-gprf-24pm

## What is CVE-2019-12363?

CVE-2019-12363 is a high-severity vulnerability in n/a, published on 11 Jul 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An CSRF issue was discovered in the JN-Jones MyBB-2FA plugin through 2014-11-05 for MyBB. An attacker can forge a request to an installed mybb2fa plugin to control its state via usercp.php?action=mybb2fa&do=deactivate (or usercp.php?action=mybb2fa&do=activate). A deactivate operation lowers the security of the targeted account by disabling two factor authentication.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2019-12363?

It affects 1 product.


Products: Mybb-2fa Project Mybb-2fa.

## How do I fix CVE-2019-12363?

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

## Is CVE-2019-12363 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12363 and fix it if it is affected.

What it is: CVE-2019-12363 is a high-severity vulnerability in n/a, published on 11 Jul 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-12363 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-2019-12363/ (Markdown: https://insights.sbomify.com/CVE-2019-12363/index.md)
```

## Sources

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

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