Skip to main content
Menu
CVEs

CVE

Toolbox for Asgaros Forum arbitrary file deletion in replace_temp_pics

CVE-2026-118521EUVD-2026-128856GHSA-3W5X-2JF4-84HFPublished Updated

6.5MediumCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

The Toolbox for Asgaros Forum plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the replace_temp_pics function in all versions up to, and including, 1.2.4. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). This vulnerability is only reachable when the site administrator has enabled the Inline Image Upload feature (disabled by default).

cve.now Index

15Pcve.now Index 15 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.5/10CVSS 6.5
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 34 if advisories confirm default setups are exposed

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-118521 (Toolbox for Asgaros Forum <= 1.2.4 - Authenticated (Subscriber+) Arbitrary File Deletion via Path Traversal via Forum Post 'message'…), 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-118521 (entry last updated 2026-11-18):
Affected:
- qualmy91 Toolbox for Asgaros Forum: through 1.2.4
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-118521 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-118521 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:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/e99c031e-6ecb-4025-8ba9-59e8e6cd1b3e?source=cve
- https://plugins.trac.wordpress.org/browser/toolbox-for-asgaros-forum/tags/1.2.4/Inc/Base/ImageUploadController.php#L276
- https://plugins.trac.wordpress.org/browser/toolbox-for-asgaros-forum/tags/1.2.4/Inc/Base/ImageUploadController.php#L237
- https://plugins.trac.wordpress.org/browser/toolbox-for-asgaros-forum/tags/1.2.4/Inc/Base/ImageUploadController.php#L60
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-118521
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-118521"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • qualmy91 Toolbox for Asgaros Forum

    through 1.2.4

Evidence 6

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-118521

Is CVE-2026-118521 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: cve.now feed data

Which versions are affected by CVE-2026-118521?

Toolbox for Asgaros Forum: through 1.2.4.Source: cve.now feed data

More CVEs