CVE-2026-122144 · Other
NO FIX YET
A cross-site request forgery flaw exists in the pico-content-editor project, a web editor for Pico CMS content, up to a specific commit. A remote attacker can trick a logged-in user's browser into sending requests the editor will accept.
first public Nov 5, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
The flaw is in an unmaintained project and applies to deployments of pico-content-editor up to the named commit. Sources state the maintainer no longer supports the product and no version information is published because it uses a rolling release. Teams running this editor on an internet-reachable site should review it; teams not running it can skip it.
Not affected if not-running-pico-content-editor, unsupported-version-not-deployed
Who cares pico-cms, pico-content-editor, self-hosted
Unknown from the sources.
No fix yet, per the sources.
A security flaw has been discovered in nliautaud pico-content-editor up to 02d5ad6c820c5050c542ab9505819b5e0a0ba1af. This vulnerability affects unknown code. The manipulation results in cross-site request forgery. The attack may be performed from remote. The exploit has been released to the public and may be used for attacks. This product utilizes a rolling release system for continuous delivery, and as such, version information for affected or updated releases is not disclosed. The vendor was contacted early about this disclosure but did not respond in any way. This vulnerability only affects products that are no longer supported by the maintainer.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.