CVE-2016-10968 Privilege escalation in n/a
High 8.8
Published
Updated
Check this codebase for CVE-2016-10968 and fix it if it is affected.
What it is: CVE-2016-10968 is a high-severity vulnerability in n/a, published on 16 Sep 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-10968 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-10968/ (Markdown: https://insights.sbomify.com/CVE-2016-10968/index.md)
The PeepSo Core plugin for WordPress allows privilege escalation via the save method in profile preferences.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2016-10968?
CVE-2016-10968 is a high-severity vulnerability in n/a, published on 16 Sep 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
The peepso-core plugin before 1.6.1 for WordPress has PeepSoProfilePreferencesAjax->save() privilege escalation.
Weakness: CWE-269
Which versions are affected by CVE-2016-10968?
It affects 1 product.
Products include Peepso Peepso.
How do I fix CVE-2016-10968?
No fix has been published for CVE-2016-10968 yet. Limit exposure of the affected software until one is available.
Is CVE-2016-10968 being exploited?
There is no known exploitation of CVE-2016-10968 in the wild and no public exploit code.
Other vulnerabilities in n/a
- CVE-2023-48746 WordPress Community by PeepSo Plugin <= 6.2.6.0 is vulnerable to Cross Site Scripting (XSS)
- CVE-2024-22158 WordPress PeepSo Core: Photos Plugin < 6.3.1.0 is vulnerable to Cross Site Scripting (XSS)
- CVE-2023-47850 WordPress Community by PeepSo Plugin <= 6.2.2.0 is vulnerable to Cross Site Scripting (XSS)
- CVE-2024-0187 Community by PeepSo < 6.3.1.2 - Reflected XSS
- CVE-2023-39925 WordPress Community by PeepSo Plugin <= 6.1.6.0 is vulnerable to Cross Site Request Forgery (CSRF)
Sources
Also known as GHSA-mhm5-5wf9-wh5m.