# CVE-2018-20853: An issue was discovered in the MailPoet Newsletters (aka wysija-newsletters) plugin before 2.8.2 for WordPress.


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 6 Nov 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h8px-936j-jcgc

## What is CVE-2018-20853?

CVE-2018-20853 is a medium-severity vulnerability in n/a, published on 6 Nov 2019. 

### Official description

An issue was discovered in the MailPoet Newsletters (aka wysija-newsletters) plugin before 2.8.2 for WordPress. The plugin is vulnerable to SPAM attacks.

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

It affects 1 product.


Products: Mailpoet Mailpoet Newsletters.

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

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

## Is CVE-2018-20853 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-4725](https://insights.sbomify.com/CVE-2014-4725/): Auth bypass in n/a (high 7.5)
- [CVE-2014-4726](https://insights.sbomify.com/CVE-2014-4726/): Unspecified vulnerability in the MailPoet Newsletters (wysija-newsletters) plugin before 2.6.8 for WordPress has unspecified impact and attack vectors. (high 7.5)
- [CVE-2014-3907](https://insights.sbomify.com/CVE-2014-3907/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-20853 is a medium-severity vulnerability in n/a, published on 6 Nov 2019. 
Exploitation: There is no known exploitation of CVE-2018-20853 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-20853/ (Markdown: https://insights.sbomify.com/CVE-2018-20853/index.md)
```

## Sources

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

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