CVE-2024-8043

CVE-2024-8043 is a medium-severity vulnerability in Seanschulte Vikinghammer Tweet with a CVSS 3.x base score of 5.4. 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 Vikinghammer Tweet WordPress plugin through 0.2.4 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack.

Frequently asked questions

What is CVE-2024-8043?
The Vikinghammer Tweet WordPress plugin through 0.2.4 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack.
How severe is CVE-2024-8043?
CVE-2024-8043 has a CVSS 3.x base score of 5.4, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and user interaction. Impact on confidentiality is low, integrity low, and availability none.
Is CVE-2024-8043 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (5th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-8043?
CVE-2024-8043 affects Seanschulte Vikinghammer Tweet. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2024-8043?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2024-8043 have an EU (EUVD) identifier?
Yes. CVE-2024-8043 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-48900.
When was CVE-2024-8043 published?
CVE-2024-8043 was published on 2024-09-17 and last updated on 2026-06-17.

References

Affected products (1)

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

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