Security readout for executives and security teams
Plain-English summary
A WordPress plugin flaw lets any logged-in user, even a Subscriber, change the recorded author of posts or attachments. This is not a site takeover issue, but it can disrupt content ownership, attribution, editorial workflows, and attachment management on sites using User Profile Builder up to 3.15.5.
Executive priority
Treat as a near-term maintenance fix, especially for sites with public registration or many low-privilege users. It is unlikely to cause full compromise alone, but it can damage content governance and should be addressed during the next patch cycle.
Technical view
CVE-2026-3139 is an insecure direct object reference in User Profile Builder’s wppb_save_avatar_value() function. Missing validation on a user-controlled key allows authenticated Subscriber+ users to reassign arbitrary posts and attachments by changing post_author. CVSS 3.1 is 4.3: network exploitable, low complexity, low privileges, no user interaction, integrity impact only.
Likely exposure
Exposure is limited to WordPress sites running the User Profile Builder plugin versions up to and including 3.15.5, where untrusted users can authenticate with Subscriber-level access or higher.
Exploitation context
No cited source states active exploitation, and this CVE is not listed as KEV in the provided data. Abuse requires an authenticated account, reducing reach, but many WordPress sites allow subscriber registration or broad user access.
Researcher notes
Sources identify the vulnerable path as wppb_save_avatar_value() and the impact as arbitrary post_author reassignment. The description states versions through 3.15.5 are affected. The provided metadata has limited affected-version structure, so confirm exact fixed version from vendor or WordPress plugin records.
Mitigation direction
- Identify WordPress sites using User Profile Builder.
- Check installed plugin version against the vendor and WordPress plugin guidance.
- Update the plugin if a fixed release is available through trusted channels.
- Restrict public or unnecessary Subscriber-level registration until remediated.
- Review user roles and remove unneeded authenticated accounts.
Validation and detection
- Confirm whether User Profile Builder is installed and enabled.
- Record the installed plugin version on each WordPress site.
- Check whether public user registration is enabled.
- Review recent post and attachment author changes for anomalies.
- Monitor WordPress logs for suspicious authenticated profile update activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-3139 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.