CVE-2019-16531 LayerBB before 1.1.4 has multiple CSRF issues, as demonstrated by changing the System Settings via admin/general.php.
High 8.8
Published
Updated
Check this codebase for CVE-2019-16531 and fix it if it is affected.
What it is: CVE-2019-16531 is a high-severity vulnerability in n/a, published on 20 Sep 2019.
Exploitation: There is no known exploitation of CVE-2019-16531 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-2019-16531/ (Markdown: https://insights.sbomify.com/CVE-2019-16531/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2019-16531?
CVE-2019-16531 is a high-severity vulnerability in n/a, published on 20 Sep 2019.
Official description
LayerBB before 1.1.4 has multiple CSRF issues, as demonstrated by changing the System Settings via admin/general.php.
Weakness: CWE-352
Which versions are affected by CVE-2019-16531?
It affects 1 product.
Products include Layerbb Layerbb.
How do I fix CVE-2019-16531?
No fix has been published for CVE-2019-16531 yet. Limit exposure of the affected software until one is available.
Is CVE-2019-16531 being exploited?
There is no known exploitation of CVE-2019-16531 in the wild and no public exploit code.
Public exploit code: 1 Exploit-DB entry.
Other vulnerabilities in n/a
Sources
Also known as GHSA-vmr6-p4cg-ph5r.