fkie_cve-2024-3631
Vulnerability from fkie_nvd
Published
2024-05-15 06:15
Modified
2025-03-25 19:15
Severity ?
4.3 (Medium) - CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Summary
The HL Twitter WordPress plugin through 2014.1.18 does not have CSRF check when unlinking twitter accounts, which could allow attackers to make logged in admins perform such actions via a CSRF attack
References
contact@wpscan.comhttps://wpscan.com/vulnerability/c59a8b49-6f3e-452b-ba9b-50b80c522ee9/
af854a3a-2127-422b-91ae-364da2661108https://wpscan.com/vulnerability/c59a8b49-6f3e-452b-ba9b-50b80c522ee9/
Impacted products
Vendor Product Version


To clipboard 

{
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "The HL Twitter WordPress plugin through 2014.1.18 does not have CSRF check when unlinking twitter accounts, which could allow attackers to make logged in admins perform such actions via a CSRF attack",
      },
      {
         lang: "es",
         value: "El complemento HL Twitter WordPress hasta 2014.1.18 no tiene verificación CSRF al desvincular cuentas de Twitter, lo que podría permitir a los atacantes hacer que los administradores registrados realicen tales acciones a través de un ataque CSRF.",
      },
   ],
   id: "CVE-2024-3631",
   lastModified: "2025-03-25T19:15:43.967",
   metrics: {
      cvssMetricV31: [
         {
            cvssData: {
               attackComplexity: "LOW",
               attackVector: "NETWORK",
               availabilityImpact: "NONE",
               baseScore: 4.3,
               baseSeverity: "MEDIUM",
               confidentialityImpact: "NONE",
               integrityImpact: "LOW",
               privilegesRequired: "NONE",
               scope: "UNCHANGED",
               userInteraction: "REQUIRED",
               vectorString: "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N",
               version: "3.1",
            },
            exploitabilityScore: 2.8,
            impactScore: 1.4,
            source: "134c704f-9b21-4f2e-91b3-4a467353bcc0",
            type: "Secondary",
         },
      ],
   },
   published: "2024-05-15T06:15:13.170",
   references: [
      {
         source: "contact@wpscan.com",
         url: "https://wpscan.com/vulnerability/c59a8b49-6f3e-452b-ba9b-50b80c522ee9/",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         url: "https://wpscan.com/vulnerability/c59a8b49-6f3e-452b-ba9b-50b80c522ee9/",
      },
   ],
   sourceIdentifier: "contact@wpscan.com",
   vulnStatus: "Awaiting Analysis",
}


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.




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.