ghsa-94q7-f538-38mf
Vulnerability from github
Published
2022-05-17 01:19
Modified
2022-05-17 01:19
Details

wp-includes/rest-api/endpoints/class-wp-rest-users-controller.php in the REST API implementation in WordPress 4.7 before 4.7.1 does not properly restrict listings of post authors, which allows remote attackers to obtain sensitive information via a wp-json/wp/v2/users request.

Show details on source website


{
   affected: [],
   aliases: [
      "CVE-2017-5487",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-200",
      ],
      github_reviewed: false,
      github_reviewed_at: null,
      nvd_published_at: "2017-01-15T02:59:00Z",
      severity: "MODERATE",
   },
   details: "wp-includes/rest-api/endpoints/class-wp-rest-users-controller.php in the REST API implementation in WordPress 4.7 before 4.7.1 does not properly restrict listings of post authors, which allows remote attackers to obtain sensitive information via a wp-json/wp/v2/users request.",
   id: "GHSA-94q7-f538-38mf",
   modified: "2022-05-17T01:19:01Z",
   published: "2022-05-17T01:19:01Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2017-5487",
      },
      {
         type: "WEB",
         url: "https://github.com/WordPress/WordPress/commit/daf358983cc1ce0c77bf6d2de2ebbb43df2add60",
      },
      {
         type: "WEB",
         url: "https://codex.wordpress.org/Version_4.7.1",
      },
      {
         type: "WEB",
         url: "https://wordpress.org/news/2017/01/wordpress-4-7-1-security-and-maintenance-release",
      },
      {
         type: "WEB",
         url: "https://wpvulndb.com/vulnerabilities/8715",
      },
      {
         type: "WEB",
         url: "https://www.exploit-db.com/exploits/41497",
      },
      {
         type: "WEB",
         url: "https://www.wordfence.com/blog/2016/12/wordfence-blocks-username-harvesting-via-new-rest-api-wp-4-7",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2017/01/14/6",
      },
      {
         type: "WEB",
         url: "http://www.securityfocus.com/bid/95391",
      },
      {
         type: "WEB",
         url: "http://www.securitytracker.com/id/1037591",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
         type: "CVSS_V3",
      },
   ],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.