baserCMS is a website development framework

Why it is Yellow

• CVSS 7.2 high

References

• https://github.com/baserproject/basercms/commit/38c778e92688e7f5d620a4c6b47ad7fb9e2c1529
• https://github.com/baserproject/basercms/commit/59dfe61e193ae3274c195c15e7b185816d2db9db
• https://github.com/baserproject/basercms/releases/tag/5.3.2
• https://github.com/baserproject/basercms/releases/tag/5.4.2
• https://github.com/baserproject/basercms/security/advisories/GHSA-xf6p-r2hc-cc6w

Original description

baserCMS is a website development framework. In versions 5.0.0 before 5.3.2 and 5.4.0 before 5.4.2, the widget-area entity serializes widgets only when the submitted value is an array, allowing a string submitted through the admin JSON API to be stored unchanged. Entity reads, including front-end rendering and API responses, deserialize the stored value with unserialize() without an allowed_classes restriction, accepting both raw and base64-encoded serialized data. An administrator, or an attacker who obtains widget-write capability through a separate vulnerability such as chained XSS, can plant an object graph that subsequently triggers on unauthenticated page requests. Two demonstrated gadget chains in the default dependency set use composer/composer ProcessExecutor::startJob() with Process::fromShellCommandline(), or logiscape/mcp-sdk-php StdioTransport::connect() with StdioServerParameters, to reach proc_open() and execute commands as the web-server user. Deserialization bypasses constructor-based readonly safeguards, and the stored payload can execute repeatedly until the database row is repaired. Unauthenticated page access is a trigger after privileged payload storage, not an unauthenticated means of initially planting the payload. This issue has been patched in versions 5.3.2 and 5.4.2.