<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-06T06:35:05.316473+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-374217</id>
    <title>EUVD-2026-374217</title>
    <updated>2026-10-06T06:35:05.421862+00:00</updated>
    <content>EUVD-2026-374217</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-374217"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-88974</id>
    <title>fkie_cve-2026-88974</title>
    <updated>2026-10-06T06:35:05.421898+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>WPGraphQL provides a GraphQL API for WordPress sites. Prior to 2.22.2, the updatePost mutation in src/Mutation/PostObjectUpdate.php checks only the collection-level edit_posts capability and the post author, but does not enforce the object-level edit_post capability or require publish_posts for public status transitions. An authenticated Contributor can therefore publish the Contributor's own draft without editorial approval or modify the Contributor's previously published post despite lacking edit_published_posts, while posts owned by other authors remain protected. This issue is fixed in version 2.22.2.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-88974"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-5mmc-8pc9-wggg</id>
    <title>GHSA-5mmc-8pc9-wggg — WPGraphQL: Contributor can publish and modify posts without the required capabilities via updatePost</title>
    <updated>2026-10-06T06:35:05.421932+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Packagist: wp-graphql/wp-graphql</p>
<p>## Summary</p>
<p>WPGraphQL 2.19.0 contains an authorization bypass in the `updatePost` mutation. An authenticated WordPress Contributor can change one of their own draft posts to `PUBLISH` despite lacking the `publish_posts` capability. The same mutation also permits the Contributor to modify their own previously published posts despite lacking `edit_published_posts` and failing WordPress's object-level `edit_post` capability check.</p>
<p>This bypasses the standard WordPress editorial workflow. The WordPress REST API correctly rejects the equivalent operations for the same user.</p>
<p>## Affected software</p>
<p>- Plugin: WPGraphQL
- Plugin slug: `wp-graphql`
- Confirmed affected version: `2.19.0`
- Plugin URL: https://wordpress.org/plugins/wp-graphql/
- Repository: https://github.com/wp-graphql/wp-graphql
- WordPress version used for testing: `7.0.2`
- WPGraphQL configuration: default settings</p>
<p>Only version 2.19.0 is claimed as confirmed because that is the version tested. The same authorization pattern appears in earlier source history, but those releases were not independently tested.</p>
<p>## Vulnerability type</p>
<p>- Broken access control / authorization bypass
- CWE-863: Incorrect Authorization
- OWASP 2021: A01 – Broken Access Control
- Minimum required role: Contributor</p>
<p>## Technical cause</p>
<p>`src/Mutation/PostObjectUpdate.php` checks only the post type's collection-level `edit_posts` capability:</p>
<p>```php
if ( ! isset( $post_type_object-&gt;cap-&gt;edit_posts ) || ! current_user_can( $post_type_object-&gt;ca…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-5mmc-8pc9-wggg"/>
  </entry>
</feed>
