# CVE-2019-13344: Auth bypass in n/a

> Unauthenticated attackers can bypass authentication to modify plugin settings in the CRUDLab WP Like Button WordPress plugin.

- **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:** 5 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-xv32-4rjr-hg8q

## What is CVE-2019-13344?

CVE-2019-13344 is a medium-severity authentication bypass vulnerability in n/a, published on 5 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An authentication bypass vulnerability in the CRUDLab WP Like Button plugin through 1.6.0 for WordPress allows unauthenticated attackers to change settings. The contains() function in wp_like_button.php did not check if the current request is made by an authorized user, thus allowing any unauthenticated user to successfully update settings, as demonstrated by the wp-admin/admin.php?page=facebook-like-button each_page_url or code_snippet parameter.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Crudlab Wp Like Button.

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

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

## Is CVE-2019-13344 being exploited?

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

Public exploit code:

- WordPress Plugin Like Button 1.6.0 - Authentication Bypass (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2023-40199](https://insights.sbomify.com/CVE-2023-40199/): WordPress WP Like Button Plugin <= 1.7.0 is vulnerable to Cross Site Request Forgery (CSRF) (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-13344 is a medium-severity authentication bypass vulnerability in n/a, published on 5 Jul 2019. 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-2019-13344 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-13344/ (Markdown: https://insights.sbomify.com/CVE-2019-13344/index.md)
```

## Sources

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

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