UBUNTU-CVE-2019-20043 (CVE-2019-20043)

Vulnerability from osv_ubuntu – Published: 2019-12-27 08:15 – Updated: 2025-10-24 04:48 – Source website
VLAI
Details

In in wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php in WordPress 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.

Severity
4.3 (Medium)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
N/A (UNKNOWN)
medium
References
To clipboard 

{
  "affected": [
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "wordpress",
            "binary_version": "4.4.2+dfsg-1ubuntu1"
          },
          {
            "binary_name": "wordpress-l10n",
            "binary_version": "4.4.2+dfsg-1ubuntu1"
          },
          {
            "binary_name": "wordpress-theme-twentyfifteen",
            "binary_version": "4.4.2+dfsg-1ubuntu1"
          },
          {
            "binary_name": "wordpress-theme-twentyfourteen",
            "binary_version": "4.4.2+dfsg-1ubuntu1"
          },
          {
            "binary_name": "wordpress-theme-twentysixteen",
            "binary_version": "4.4.2+dfsg-1ubuntu1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:16.04:LTS",
        "name": "wordpress",
        "purl": "pkg:deb/ubuntu/wordpress@4.4.2+dfsg-1ubuntu1?arch=source\u0026distro=xenial"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "4.3+dfsg-1",
        "4.3.1+dfsg-1",
        "4.4+dfsg-1",
        "4.4.1+dfsg-1",
        "4.4.2+dfsg-1",
        "4.4.2+dfsg-1ubuntu1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "wordpress",
            "binary_version": "4.9.5+dfsg1-1"
          },
          {
            "binary_name": "wordpress-l10n",
            "binary_version": "4.9.5+dfsg1-1"
          },
          {
            "binary_name": "wordpress-theme-twentyfifteen",
            "binary_version": "4.9.5+dfsg1-1"
          },
          {
            "binary_name": "wordpress-theme-twentyseventeen",
            "binary_version": "4.9.5+dfsg1-1"
          },
          {
            "binary_name": "wordpress-theme-twentysixteen",
            "binary_version": "4.9.5+dfsg1-1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:18.04:LTS",
        "name": "wordpress",
        "purl": "pkg:deb/ubuntu/wordpress@4.9.5+dfsg1-1?arch=source\u0026distro=bionic"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "4.8.2+dfsg-2",
        "4.8.3+dfsg-1",
        "4.9.1+dfsg-1",
        "4.9.2+dfsg-1",
        "4.9.4+dfsg-1",
        "4.9.5+dfsg1-1"
      ]
    }
  ],
  "aliases": [],
  "details": "In in wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php in WordPress 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.",
  "id": "UBUNTU-CVE-2019-20043",
  "modified": "2025-10-24T04:48:07Z",
  "published": "2019-12-27T08:15:00Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2019-20043"
    },
    {
      "type": "REPORT",
      "url": "https://core.trac.wordpress.org/changeset/46893/trunk"
    },
    {
      "type": "REPORT",
      "url": "https://github.com/WordPress/wordpress-develop/commit/1d1d5be7aa94608c04516cac4238e8c22b93c1d9"
    },
    {
      "type": "REPORT",
      "url": "https://wordpress.org/news/2019/12/wordpress-5-3-1-security-and-maintenance-release/"
    },
    {
      "type": "REPORT",
      "url": "https://wpvulndb.com/vulnerabilities/9973"
    },
    {
      "type": "REPORT",
      "url": "https://www.cve.org/CVERecord?id=CVE-2019-20043"
    }
  ],
  "related": [],
  "schema_version": "1.7.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N",
      "type": "CVSS_V3"
    },
    {
      "score": "medium",
      "type": "Ubuntu"
    }
  ],
  "upstream": [
    "CVE-2019-20043"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.