CVE-2024-3631

CVE-2024-3631 is a medium-severity vulnerability in Dachande663 Hl Twitter with a CVSS 3.x base score of 4.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-352.

Key facts

Description

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

Frequently asked questions

What is CVE-2024-3631?
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
How severe is CVE-2024-3631?
CVE-2024-3631 has a CVSS 3.x base score of 4.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is none, integrity low, and availability none.
Is CVE-2024-3631 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (11th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-3631?
CVE-2024-3631 affects Dachande663 Hl Twitter. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2024-3631?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2024-3631 have an EU (EUVD) identifier?
Yes. CVE-2024-3631 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-32210.
When was CVE-2024-3631 published?
CVE-2024-3631 was published on 2024-05-15 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Dachande663 Hl Twitter

All CVEs affecting Dachande663 Hl Twitter →

Other CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities

Browse all CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities →