---
id: "CVE-2026-103479"
page: "https://infrastack.ai/live/CVE-2026-103479"
kind: "vulnerability"
aliases: ["CVE-2026-103479"]
title: "WordPress Pubjet plugin: subscribers can overwrite API token, gaining editor rights"
severity: "high"
cvss: 7.6
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "pubjet", "self-hosted", "wordpress"]
not_affected_if: ["no-subscriber-accounts", "plugin-not-installed"]
published_at: "2026-11-06T12:17:15+00:00"
first_seen_at: "2026-11-06T12:41:48+00:00"
updated_at: "2026-11-06T12:42:43+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-103479", "first_seen_at": "2026-11-06T12:41:48+00:00"}]
exploit_sources: []
---

# WordPress Pubjet plugin: subscribers can overwrite API token, gaining editor rights

Link for people: https://infrastack.ai/live/CVE-2026-103479 (this .md is for agents)

The Pubjet WordPress plugin up to and including 5.4.8 has an AJAX handler that writes an attacker-supplied token into the site's settings without any permission or nonce check. A logged-in Subscriber can set the plugin's API credential to a value of their choosing and then use it to create, edit and delete reportage posts and change plugin state.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed Pubjet plugin version in the WordPress admin plugin list or `wp plugin get pubjet --field=version`
- Look for the `pubjet-check-token` AJAX action registered in the plugin code
- Review whether any Subscriber-level accounts exist on the site

## Fix

- Pubjet plugin: versions above `5.4.8` (the fixed version is not named in the sources; check the vendor's release notes)

## Timeline

- 2026-11-06T12:41:48+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-103479

## From the sources

The Pubjet | پاب‌جت plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 5.4.8. This is due to the `checkToken()` AJAX handler — registered under `wp_ajax_pubjet-check-token` — performing no capability check and no nonce verification before unconditionally writing the attacker-supplied `token` GET parameter directly into the site-wide `pubjet_settings` option via `pubjet_update_setting()`, prior to any remote validation. This makes it possible for authenticated attackers, with Subscriber-level access and above, to overwrite the plugin's stored REST API credential with an attacker-chosen value, immediately elevating their effective privileges to those of an authorized Pubjet API client and enabling them to invoke otherwise-restricted endpoints — `createReportage`, `updateReportage`, `deleteReportage`, `toggleCopyright`, and `createBacklink` — to create, modify, and delete arbitrary reportage posts and manipulate plugin state that Subscribers cannot normally access. The privilege escalation is self-reinforcing: because `RestApi::isTokenValid()` authenticates solely by comparing the incoming `Authorization` header against the value returned by `pubjet_token()`, which reads from the same option the unprotected handler writes to, the attacker-planted token is trusted as legitimate on all subsequent requests.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_