CVE-2016-10885 Cross-site request forgery in n/a
High 8.8
Published
Updated
Check this codebase for CVE-2016-10885 and fix it if it is affected.
What it is: CVE-2016-10885 is a high-severity vulnerability in n/a, published on 14 Aug 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-10885 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-2016-10885/ (Markdown: https://insights.sbomify.com/CVE-2016-10885/index.md)
A Cross-Site Request Forgery vulnerability in the wp-editor WordPress plugin allows attackers to perform unauthorized actions on behalf of authenticated users.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2016-10885?
CVE-2016-10885 is a high-severity vulnerability in n/a, published on 14 Aug 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
The wp-editor plugin before 1.2.6 for WordPress has CSRF.
Weakness: CWE-352
Which versions are affected by CVE-2016-10885?
It affects 1 product.
Products include Benjaminrojas Wp Editor.
How do I fix CVE-2016-10885?
No fix has been published for CVE-2016-10885 yet. Limit exposure of the affected software until one is available.
Is CVE-2016-10885 being exploited?
There is no known exploitation of CVE-2016-10885 in the wild and no public exploit code.
Other vulnerabilities in n/a
- CVE-2016-10886 Missing authorization in n/a
- CVE-2025-3294 WP Editor <= 1.2.9.1 - Authenticated (Administrator+) Directory Traversal to Arbitrary File Update
- CVE-2022-2446 WP Editor <= 1.2.9 - Authenticated (Admin+) PHAR Deserialization
- CVE-2021-24151 WP Editor < 1.2.7 - Authenticated SQL injection
- CVE-2024-25591 WordPress WP Editor plugin <=1.2.7 - Sensitive Data Exposure vulnerability
Sources
Also known as GHSA-g7vh-w82q-6c7j.