CVE-2018-21011 Information disclosure in n/a
High 7.5
Published
Updated
Check this codebase for CVE-2018-21011 and fix it if it is affected.
What it is: CVE-2018-21011 is a high-severity vulnerability in n/a, published on 9 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-21011 in the wild and no public exploit code.
Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2018-21011/ (Markdown: https://insights.sbomify.com/CVE-2018-21011/index.md)
An attacker can access unauthorized user and donation details in the charitable WordPress plugin.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2018-21011?
CVE-2018-21011 is a high-severity vulnerability in n/a, published on 9 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
The charitable plugin before 1.5.14 for WordPress has unauthorized access to user and donation details.
Weakness: CWE-200
Which versions are affected by CVE-2018-21011?
It affects 1 product.
Products include Wpcharitable Charitable.
How do I fix CVE-2018-21011?
No fix has been published for CVE-2018-21011 yet. Limit exposure of the affected software until one is available.
Is CVE-2018-21011 being exploited?
There is no known exploitation of CVE-2018-21011 in the wild and no public exploit code.
Other vulnerabilities in n/a
- CVE-2024-8791 Auth bypass in Charitable – Donation Plugin for WordPress – Fundraising with Recurring Donations & More
- CVE-2023-4404 Donation Forms by Charitable <= 1.7.0.12 - Unauthenticated Privilege Escalation
- CVE-2022-47441 WordPress Charitable Plugin <= 1.7.0.10 is vulnerable to Cross Site Scripting (XSS)
- CVE-2023-47816 WordPress Charitable Plugin <= 1.7.0.13 is vulnerable to Cross Site Scripting (XSS)
- CVE-2021-24531 Charitable – Donation Plugin < 1.6.51 - Authenticated Stored Cross-Site Scripting (XSS)
Sources
Also known as GHSA-fg8w-mqjp-j9r9.