# CVE-2018-15876: Security feature bypass in n/a

> Attackers can bypass CAPTCHA protections on login and registration forms by automating requests within a single session, enabling brute-force attacks.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Aug 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-hhgg-9qff-8q38

## What is CVE-2018-15876?

CVE-2018-15876 is a medium-severity vulnerability in n/a, published on 26 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the ajax-bootmodal-login plugin 1.4.3 for WordPress. The register form, login form, and password-recovery form require solving a CAPTCHA to perform actions. However, this is required only once per user session, and therefore one could send as many requests as one wished by automation.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-15876?

It affects 1 product.


Products: Ajax Bootmodal Login Project Ajax Bootmodal Login.

## How do I fix CVE-2018-15876?

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

## Is CVE-2018-15876 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-15876 and fix it if it is affected.

What it is: CVE-2018-15876 is a medium-severity vulnerability in n/a, published on 26 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-15876 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-2018-15876/ (Markdown: https://insights.sbomify.com/CVE-2018-15876/index.md)
```

## Sources

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

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