Radar sectionsDatabase
Check my site
WordPress plugin

Co-Authors, Multiple Authors and Guest Authors in an Author Box with PublishPress Authors <= 4.7.1 — Insecure Direct Object Reference to Authenticated (Author+) Arbitrary User Email Update and Account Takeover

CVE-2024-9215Published · Updated

Action summary

Affected: ≤4.7.1Update to 4.7.2 or newer

All remediation steps
Severity
High8.8
CVSS
8.8
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:L Privileges required
Low
UI:N User interaction
None
S:U Scope
Unchanged
C:H Confidentiality
High
I:H Integrity
High
A:H Availability
High
Weakness
CWE-639 Authorization Bypass Through User-Controlled Key
Required access
Unknown
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

Co-Authors, Multiple Authors and Guest Authors in an Author Box with PublishPress Authors publishpress-authors

  1. Affected≤ 4.7.1
  2. Patched in4.7.2

Update to 4.7.2 or newer.

You are affected if you run ≤ 4.7.1. Version 4.7.2 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Co-Authors, Multiple Authors and Guest Authors in an Author Box with PublishPress Authors.
  • No admin access? Run a passive check of your site. It reads public files only.

What to do

  1. Update to version 4.7.2, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Co-Authors, Multiple Authors and Guest Authors in an Author Box with PublishPress Authors to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to wesley (wcraft).

The Co-Authors, Multiple Authors and Guest Authors in an Author Box with PublishPress Authors plugin for WordPress is vulnerable to Insecure Direct Object Reference to Privilege Escalation/Account Takeover in all versions up to, and including, 4.7.1 via the action_edited_author() due to missing validation on the 'authors-user_id' user controlled key. This makes it possible for authenticated attackers, with Author-level access and above, to update arbitrary user accounts email addresses, including administrators, which can then be leveraged to reset that user's account password and gain access.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Co-Authors, Multiple Authors and Guest Authors in an Author Box with PublishPress Authors

All 8
More vulnerabilities in Co-Authors, Multiple Authors and Guest Authors in an Author Box with PublishPress Authors
SeverityVulnerabilityCVEPublished
Medium6.4Authenticated (Subscriber+) Stored Cross-Site Scripting via display_name profile-sync into author term name
≤4.17.0Update to 4.18.0
CVE-2026-111592
Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting
≤4.17.0Update to 4.18.0
CVE-2026-115610
Medium5.4Authenticated (Author+) Stored Cross-Site Scripting via 'profile_fields_user_email_value_prefix' Parameter
≤4.15.0Update to 4.16.0
CVE-2026-85657
Medium5.3Missing Authorization
≤4.10.1Update to 4.11.0
CVE-2026-25309
Medium4.3Missing Authorization
≤4.10.1Update to 4.11.0
CVE-2026-25330

Timeline

  1. CVE published

    Severity high, CVSS 8.8

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?