CVE-2026-103479
Last modified
CVE-2026-103479 is a high-severity vulnerability rated 7.6/10 on the CVSS scale. 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.
Description
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.
Metrics
Weakness Enumeration
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-103479?
How severe is CVE-2026-103479?
How do I fix CVE-2026-103479?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-103472restbed through 5.0.0 accepts WebSocket frames with declared…7.5
- CVE-2026-103473Deno versions 2.7.0 through 2.9.7 on Windows contain a comma…8.1
- CVE-2026-103474yii2-starter-kit through 4.2.0 fails to validate file types …8.8
- CVE-2026-103475yii2-starter-kit through 4.2.0 exposes the Yii debug and Gii…9.1
- CVE-2026-103476yii2-starter-kit through 4.2.0 fails to validate article pub…5.3
- CVE-2026-103478The Premium Packages – Sell Digital Products Securely plugin…6.4
- CVE-2026-103480The Tourfic – AI Powered Travel Booking, Hotel Booking & Car…6.4
- CVE-2026-103481The Gwolle Guestbook plugin for WordPress is vulnerable to R…6.1
- CVE-2026-103482The Simple Newsletter Plugin – Noptin plugin for WordPress i…5.4
- CVE-2026-103484IVFFlat index build in pgvector before 0.8.7 allows a databa…8.8
- CVE-2026-103485The Extensions for Leaflet Map plugin for WordPress is vulne…5.4
- CVE-2026-103488In JetBrains YouTrack before 2026.2.19422 missing authorisat…7.1
Are you affected by CVE-2026-103479?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
