CVE-2020-36170 Business logic in n/a
Medium 5.3
Published
Updated
Check this codebase for CVE-2020-36170 and fix it if it is affected.
What it is: CVE-2020-36170 is a medium-severity vulnerability in n/a, published on 6 Jan 2021. 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-2020-36170 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-2020-36170/ (Markdown: https://insights.sbomify.com/CVE-2020-36170/index.md)
The Ultimate Member WordPress plugin mishandles hidden timestamp fields, allowing attackers to bypass intended form restrictions.
- 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-2020-36170?
CVE-2020-36170 is a medium-severity vulnerability in n/a, published on 6 Jan 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
The Ultimate Member plugin before 2.1.13 for WordPress mishandles hidden name="timestamp" fields in forms.
Which versions are affected by CVE-2020-36170?
It affects 1 product.
Products include Ultimatemember Ultimate Member.
How do I fix CVE-2020-36170?
No fix has been published for CVE-2020-36170 yet. Limit exposure of the affected software until one is available.
Is CVE-2020-36170 being exploited?
There is no known exploitation of CVE-2020-36170 in the wild and no public exploit code.
Other vulnerabilities in n/a
- CVE-2020-36155 Privilege escalation in n/a
- CVE-2020-36157 Privilege escalation in n/a
- CVE-2020-36156 Privilege escalation in n/a
- CVE-2024-1071 SQL injection in Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin
- CVE-2023-3460 Ultimate Member < 2.6.7 - Unauthenticated Privilege Escalation
Sources
Also known as GHSA-g3vc-mp64-64gm.