Security readout for executives and security teams
Plain-English summary
CVE-2025-60175 is a medium-severity SSRF issue in the WordPress PopAd plugin through version 1.0.4. An administrator-level attacker could make the site send requests to unintended locations, potentially exposing limited internal data or changing limited state. The source bundle does not name active exploitation or a fixed version.
Executive priority
Treat this as a moderate, targeted WordPress plugin risk. It is not shown as actively exploited, but sites running PopAd should be identified and remediated because administrator account compromise could turn this into an internal network exposure path.
Technical view
The CVE describes administrator SSRF in vynnus PopAd for WordPress, package popad, affecting versions up to 1.0.4. CVSS 3.1 is 4.4 with network access, high complexity, high privileges, no user interaction, changed scope, and low confidentiality and integrity impact. No affected CPEs or endpoint details are provided.
Likely exposure
Exposure is likely limited to WordPress sites with PopAd installed at version 1.0.4 or earlier. Risk is lower than unauthenticated SSRF because exploitation requires administrator privileges and high complexity, but compromised admin accounts could still abuse it.
Exploitation context
The bundle marks KEV as false and cites no public exploitation evidence. Patchstack is listed as the vulnerability database source, but the provided data does not include exploit status, proof-of-concept details, or observed attacks.
Researcher notes
Evidence is sparse: the bundle provides CVSS, CWE-918, administrator SSRF, product name, and version boundary, but no vulnerable parameter, endpoint, patch version, or exploit telemetry. Avoid assuming broader WordPress exposure beyond PopAd <= 1.0.4.
Mitigation direction
- Inventory WordPress sites for the PopAd plugin and version.
- Check vendor or Patchstack guidance for a fixed release or recommended action.
- Update PopAd if a supported fixed version is available.
- Disable or remove PopAd where it is not business-critical.
- Restrict and review WordPress administrator access.
- Apply outbound network controls from web servers where feasible.
Validation and detection
- Confirm whether PopAd is installed on each WordPress instance.
- Record installed PopAd versions and flag 1.0.4 or earlier.
- Review WordPress administrator accounts for unnecessary or stale access.
- Check web server egress logs for unusual internal or metadata-service requests.
- Monitor vendor and Patchstack pages for remediation details.
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-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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 lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material 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-60175 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
- 4.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N
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:H/UI:N/S:C/C:L/I:L/A:N1.32.7PatchstackVulnerability scoring details
Base CVSS 3.1 score
4.4MediumVector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N
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://patchstack.com/database/wordpress/plugin/popad/vulnerability/wordpress-popad-plugin-1-0-4-server-side-request-forgery-ssrf-vulnerability?_s_id=cveCVE reference, Patchstack · 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.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.