Description

Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2019-20043. Reason: This candidate is a duplicate of CVE-2019-20043. Notes: All CVE users should reference CVE-2019-20043 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage

INFO

Published Date :

Jan. 9, 2020, 3:15 a.m.

Last Modified :

Nov. 7, 2023, 3:05 a.m.

Remotely Exploitable :

No

Impact Score :

Exploitability Score :

Public PoC/Exploit Available at Github

CVE-2019-16788 has a 4 public PoC/Exploit available at Github. Go to the Public Exploits tab to see the list.

Affected Products

The following products are affected by CVE-2019-16788 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

None

Updated: 2 months, 4 weeks ago
0 stars 0 fork 0 watcher
Born at : Jan. 30, 2025, 9:01 a.m. This repo has been linked 173 different CVEs too.

WordPress Pen Testing

Updated: 8 months, 3 weeks ago
3 stars 0 fork 0 watcher
Born at : Oct. 23, 2022, 8:42 p.m. This repo has been linked 100 different CVEs too.

Desarrollo del CTF DerpNStink

Updated: 4 years ago
0 stars 1 fork 1 watcher
Born at : April 22, 2021, 1:40 p.m. This repo has been linked 41 different CVEs too.

Desarrollo del CTF SYMFONOS

Updated: 4 years, 1 month ago
0 stars 0 fork 0 watcher
Born at : March 28, 2021, 1:13 a.m. This repo has been linked 46 different CVEs too.

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2019-16788 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2019-16788 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • CVE Source Update by [email protected]

    Nov. 07, 2023

    Action Type Old Value New Value
    Changed Source MITRE GitHub, Inc.
  • CVE Modified by [email protected]

    Nov. 07, 2023

    Action Type Old Value New Value
    Changed Description ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2019-20043. Reason: This candidate is a duplicate of CVE-2019-20043. Notes: All CVE users should reference CVE-2019-20043 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage. Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2019-20043. Reason: This candidate is a duplicate of CVE-2019-20043. Notes: All CVE users should reference CVE-2019-20043 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage
  • CVE Modified by [email protected]

    Mar. 11, 2020

    Action Type Old Value New Value
    Changed Description In WordPress versions from 3.7 to 5.3.0, authenticated users who do not have the rights to publish a post are able to mark posts as sticky or unsticky via the REST API. For example, the contributor role does not have such rights, but this allowed them to bypass that. This has been patched in WordPress 5.3.1, along with all the previous WordPress versions from 3.7 to 5.3 via a minor release. Automatic updates are enabled by default for minor releases and we strongly recommend that you keep them enabled. ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2019-20043. Reason: This candidate is a duplicate of CVE-2019-20043. Notes: All CVE users should reference CVE-2019-20043 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage.
    Removed CVSS V3.1 GitHub, Inc. AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
    Removed Reference https://github.com/WordPress/wordpress-develop/commit/1d1d5be7aa94608c04516cac4238e8c22b93c1d9 [Patch, Third Party Advisory]
    Removed Reference https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-g7rg-hchx-c2gw [Third Party Advisory]
    Removed Reference https://wordpress.org/news/2019/12/wordpress-5-3-1-security-and-maintenance-release/ [Vendor Advisory]
    Removed Reference https://wpvulndb.com/vulnerabilities/9973 [Third Party Advisory]
    Removed CWE GitHub, Inc. CWE-79
  • CVE Rejected by [email protected]

    Mar. 11, 2020

    Action Type Old Value New Value
  • Initial Analysis by [email protected]

    Jan. 17, 2020

    Action Type Old Value New Value
    Added CVSS V2 NIST (AV:N/AC:L/Au:S/C:N/I:P/A:N)
    Added CVSS V3.1 NIST AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
    Changed Reference Type https://github.com/WordPress/wordpress-develop/commit/1d1d5be7aa94608c04516cac4238e8c22b93c1d9 No Types Assigned https://github.com/WordPress/wordpress-develop/commit/1d1d5be7aa94608c04516cac4238e8c22b93c1d9 Patch, Third Party Advisory
    Changed Reference Type https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-g7rg-hchx-c2gw No Types Assigned https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-g7rg-hchx-c2gw Third Party Advisory
    Changed Reference Type https://wordpress.org/news/2019/12/wordpress-5-3-1-security-and-maintenance-release/ No Types Assigned https://wordpress.org/news/2019/12/wordpress-5-3-1-security-and-maintenance-release/ Vendor Advisory
    Changed Reference Type https://wpvulndb.com/vulnerabilities/9973 No Types Assigned https://wpvulndb.com/vulnerabilities/9973 Third Party Advisory
    Added CWE NIST CWE-287
    Added CPE Configuration OR *cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:* versions from (including) 3.7 up to (including) 5.3.0
  • CVE Modified by [email protected]

    Jan. 10, 2020

    Action Type Old Value New Value
    Added Reference https://wpvulndb.com/vulnerabilities/9973 [No Types Assigned]
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2019-16788 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2019-16788 weaknesses.

Exploit Prediction

EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.

0.24 }} 0.00%

score

0.63208

percentile

NONE - Vulnerability Scoring System
© cvefeed.io
Latest DB Update: Apr. 29, 2025 16:09