cve.bz

CVE-2026-118064 Advance Guest Post <= 1.9 - Unauthenticated Arbitrary File Upload via featured_action

9.8 criticalEPSS 0.2%

Critical (9.8) in unknown advance guest post. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
The Advance Guest Post WordPress plugin through 1.9 does not properly restrict or validate file uploads, authorizing an upload action with a nonce exposed to every front-end visitor and checking only a file's leading bytes, allowing unauthenticated users to upload arbitrary PHP files and execute code remotely. Successful exploitation additionally requires the target to run PHP 7.x; on PHP 8.0 and later the vulnerable code path raises a fatal error before the file is written.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% estimated probability of exploitation activity in the next 30 days; 5th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-434 Unrestricted Upload of File with Dangerous Type
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
Assigned by
WPScan (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-118064 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-118064?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-118064?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-118064 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-118064

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-118064](https://cve.bz/cve/badge/CVE-2026-118064.svg)](https://cve.bz/cve/CVE-2026-118064)

HTML:

<a href="https://cve.bz/cve/CVE-2026-118064"><img src="https://cve.bz/cve/badge/CVE-2026-118064.svg" alt="CVE-2026-118064"></a>

Affected

  • unknown:advance guest post

Attack patterns (CAPEC)

  • CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. The NVD deferred its analysis
  2. Scored 9.8 critical

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON