Adamsolymosi maintains a narrowly scoped vulnerability footprint centered on its ContentLock product, with the observed weakness signal concentrated on cross-site request forgery (CSRF) flaws in its web-facing components. Treat this as a compact vendor profile; live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Adamsolymosi over time
Signals from CVEs in this vendor scope (3 CVEs).
3 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2024-6024HIGH The ContentLock WordPress plugin through 1.0.3 does not have CSRF check in place when deleting groups or emails, which could allow attackers to make a logged in admin remove them v | Jul 12, 2024 | 8.8 | 25 | NO | NO |
CVE-2024-6023HIGH The ContentLock WordPress plugin through 1.0.3 does not have CSRF check in place when adding emails, which could allow attackers to make a logged in admin perform such action via a | Jul 12, 2024 | 8.8 | 24 | NO | NO |
CVE-2024-6022HIGH The ContentLock WordPress plugin through 1.0.3 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a | Jul 12, 2024 | 8.8 | 24 | NO | NO |
Signals from CVEs in this vendor scope (3 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Adamsolymosi.
Media articles that mention a CVE ID that affects a product developed by Adamsolymosi — matched by CVE ID, not by vendor name.