CVE-2026-108685 WP Post Author < 4.2.0 - Unauthenticated Modification of the First User Account's Profile Fields
Low 3.7
Published
Updated
Check this codebase for CVE-2026-108685 and fix it if it is affected.
What it is: CVE-2026-108685 is a low-severity vulnerability in Unknown WP Post Author, published on 29 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-108685 in the wild and no public exploit code.
Affected product: Unknown WP Post Author. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-108685/ (Markdown: https://insights.sbomify.com/CVE-2026-108685/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-108685?
CVE-2026-108685 is a low-severity vulnerability in Unknown WP Post Author, published on 29 Oct 2026.
Official description
The WP Post Author WordPress plugin before 4.2.0 does not check that the account was created before updating its profile during front-end registration, allowing unauthenticated users to overwrite the display name, nickname and website of the first user account, which is normally the administrator, when a registration form declares one of those fields.
Weakness: CWE-862
Which versions are affected by CVE-2026-108685?
How do I fix CVE-2026-108685?
No fix has been published for CVE-2026-108685 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-108685 being exploited?
There is no known exploitation of CVE-2026-108685 in the wild and no public exploit code.
Sources
Also known as GHSA-p922-mx52-2wrj.