Security readout for executives and security teams
Plain-English summary
This affects the Iptanus File Upload WordPress plugin before 5.1.7. If a site allows authenticated users to upload files and uses the duplicate policy “maintain both,” a timing flaw can let one user overwrite another user’s uploaded files. Business impact is mainly data integrity and limited availability risk, not direct data theft per the CVSS details.
Executive priority
Prioritize remediation on WordPress sites that accept uploads from many authenticated users, such as customer portals, communities, or contributor workflows. This is not rated critical, but the ability to overwrite user files can create business disruption, trust issues, and content integrity problems.
Technical view
CVE-2025-15546 is a CWE-362 race condition in file handling. With duplicatepolicy set to “maintain both,” a TOCTOU gap between file-existence checking and file writing can allow an authenticated attacker to overwrite files uploaded by other users. CVSS 3.1 is 5.4: AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:L.
Likely exposure
WordPress sites running Iptanus File Upload before 5.1.7 are potentially exposed, especially where authenticated users can upload files and the duplicatepolicy setting is configured to “maintain both.” Sites not using this plugin or not using that setting are less likely exposed based on available information.
Exploitation context
Exploitation requires network access, low-privileged authentication, user interaction, and high attack complexity according to the CVSS vector. The bundle does not indicate CISA KEV listing or confirmed active exploitation. WPScan is referenced as a vulnerability database entry with exploit-related tagging, but no exploitation campaign is provided here.
Researcher notes
The provided data identifies the vulnerable condition and fixed version but does not include detailed vendor advisory text. Treat scope carefully: the described overwrite affects files uploaded by other users, not arbitrary server files. Avoid assuming unauthenticated exploitation or broader filesystem compromise without additional evidence.
Mitigation direction
- Update Iptanus File Upload to version 5.1.7 or later.
- Review plugin settings for duplicatepolicy set to “maintain both.”
- Restrict upload access to trusted authenticated users where possible.
- Check vendor and WPScan guidance for any additional remediation details.
- Back up uploaded files before making plugin or configuration changes.
Validation and detection
- Inventory WordPress sites for the Iptanus File Upload plugin.
- Confirm the installed plugin version is 5.1.7 or later.
- Check whether duplicatepolicy is configured to “maintain both.”
- Review upload logs for unexpected overwrites or file replacement events.
- Confirm only intended user roles can upload files.
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-362: 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 lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-15546 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
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:L
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.
SSVC decision data
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:H/PR:L/UI:R/S:U/C:N/I:H/A:L1.24.2CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://wpscan.com/vulnerability/06e33418-1644-49a1-b012-122046604109/CVE reference, WPScan · exploit, vdb-entry
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.
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.