CVE-2024-3824: Base64 Encoder/Decoder <= 0.9.2 - Settings Reset via CSRF
First published: Wed May 15 2024(Updated: )
The Base64 Encoder/Decoder WordPress plugin through 0.9.2 does not have CSRF check in place when resetting its settings, which could allow attackers to make a logged in admin reset them via a CSRF attack
Credit: contact@wpscan.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| WordPress Base64 Encoder/Decoder | <=0.9.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2024-3824?
CVE-2024-3824 is classified as a medium severity vulnerability due to the lack of CSRF protection allowing unauthorized actions by attackers.
How do I fix CVE-2024-3824?
To fix CVE-2024-3824, update the Base64 Encoder/Decoder WordPress plugin to the latest version that addresses this vulnerability.
Who is affected by CVE-2024-3824?
CVE-2024-3824 affects users of the Base64 Encoder/Decoder WordPress plugin version 0.9.2 and earlier.
What kind of attacks can exploit CVE-2024-3824?
CVE-2024-3824 can be exploited through Cross-Site Request Forgery (CSRF) attacks, allowing attackers to reset settings without authorization.
What are the potential impacts of CVE-2024-3824?
The potential impacts of CVE-2024-3824 include unauthorized changes to the plugin's settings by a malicious user, compromising site integrity.
- agent/title
- agent/type
- agent/description
- agent/references
- agent/first-publish-date
- agent/author
- collector/epss-latest
- source/FIRST
- agent/epss
- agent/weakness
- agent/source
- collector/mitre-cve
- source/MITRE
- collector/nvd-api
- source/NVD
- agent/severity
- agent/last-modified-date
- agent/tags
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/event
- agent/softwarecombine
- vendor/wordpress
- canonical/wordpress base64 encoder/decoder