WP Staging Pro <= 6.1.2 - Unauthenticated Information Exposure via getOutdatedPluginsRequest Function
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-200.
Summary
The WP STAGING Pro WordPress Backup Plugin for WordPress is vulnerable to Information Exposure in all versions up to and including 6.1.2 due to missing capability checks on the getOutdatedPluginsRequest() function. This makes it possible for unauthenticated attackers to reveal outdated installed active or inactive plugins.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2025-3104
- 2026-10-03 Alias added: GHSA-7wh6-6h78-phxw
References
More WPStaging vulnerabilities
- TI-2024-04157 Migration Backup Restore < 3.5.0 - Admin+ SSRF CVSS 3.1HIGH 7.5
- TI-2023-06590 WP STAGING WordPress Backup Plugin < 3.2.0 - Unauthorized Sensitive Data Exposure CVSS 3.1HIGH 7.5
- TI-2024-02146 WP Staging < 3.4.0, 5.4.0 (Pro Version) - Admin+ Stored XSS CVSS 3.1MEDIUM 4.8
- TI-2024-05159 WP STAGING PRO - Backup Duplicator & Migration <= 5.6.0 - Cross-Site Request Forgery to Limited Local File Inclusion CVSS 3.1HIGH 8.8
- TI-2023-05619 WP Staging (Free < 3.1.3, Pro < 5.1.3) - Unauthenticated Backup Download CVSS 3.1HIGH 7.5
- TI-2024-03436 WP STAGING <= 3.4.3 and WP STAGING Pro <= 5.4.3 - Sensitive Information Exposure via Log File CVSS 3.1MEDIUM 5.3
Sources
- CVE-2025-3104 · CVE Program
- CVE-2025-3104 · NVD
- FIRST EPSS
- GHSA-7wh6-6h78-phxw · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences