A specially-crafted Javascript file can lead to arbitrary code execution. To trigger this vulnerability, an attacker can send an HTTP request to inject Javascript in a post to trick an administrator into visiting the post.A stored XSS vulnerability exists in the `twitter` field for a user.Ī code execution vulnerability exists in the Statement Bindings functionality of Ghost Foundation node-sqlite3 5.1.1. Default installations of Ghost allow non-administrator users to inject arbitrary Javascript in posts, which allow privilege escalation to administrator via XSS. To trigger this vulnerability, an attacker can send an HTTP request to inject Javascript in a post to trick an administrator into visiting the post.A stored XSS vulnerability exists in the `facebook` field for a user.Īn insecure default vulnerability exists in the Post Creation functionality of Ghost Foundation Ghost 5.9.4. To trigger this vulnerability, an attacker can send an HTTP request to inject Javascript in a post to trick an administrator into visiting the post.A stored XSS vulnerability exists in the `codeinjection_head` for a post.Īn insecure default vulnerability exists in the Post Creation functionality of Ghost Foundation Ghost 5.9.4. To trigger this vulnerability, an attacker can send an HTTP request to inject Javascript in a post to trick an administrator into visiting the post.A stored XSS vulnerability exists in the `codeinjection_foot` for a post.Īn insecure default vulnerability exists in the Post Creation functionality of Ghost Foundation Ghost 5.9.4.
NOTE: the vendor's position is that this behavior has no security impact.Īn insecure default vulnerability exists in the Post Creation functionality of Ghost Foundation Ghost 5.9.4. Ghost 5.35.0 allows authorization bypass: contributors can view draft posts of other users, which is arguably inconsistent with a security policy in which a contributor's draft can only be read by editors until published by an editor.
0 kommentar(er)
