CVE-2025-47733
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedServer-Side Request Forgery (SSRF) in Microsoft Power Apps allows an unauthorized attacker to disclose information over a network
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceServer-Side Request Forgery (SSRF) vulnerability in Microsoft Power Apps enables unauthorized attackers to make the service perform requests to arbitrary URLs, potentially accessing internal resources and disclosing sensitive information over the network.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Power Apps is deployed in your tenantUse the Power Platform admin center (admin.powerplatform.microsoft.com) or run 'Get-AdminPowerApp' PowerShell cmdlet to list Power Apps in your environmentAffected if Any Power Apps application exists in your tenant - all versions are affected by this SSRF vulnerability
-
Check for canvas apps with URL input capabilitiesReview canvas apps in the Power Apps maker portal (make.powerapps.com) for text input controls, data source connections, or custom connectors that accept user-provided URLs or endpointsAffected if Users can input or provide URLs through app controls that trigger server-side HTTP requests
-
Identify data sources and connectors that accept URLsAudit connectors in your Power Apps (Data > Data sources) - look for HTTP connectors, custom connectors, or any data source that performs web requests based on user inputAffected if Any Power App uses connectors that make outbound HTTP requests based on user-supplied URLs or dynamic endpoints
-
Review custom connectors for URL handlingCheck the Power Platform admin center for custom connectors (https://admin.powerplatform.microsoft.com/resources/connectors) that may process URLs provided by app usersAffected if Custom connectors exist that accept and process arbitrary URLs from users
-
Check for Power Automate flows triggered by Power AppsReview Power Automate flows associated with your Power Apps (through the Power Apps maker portal or Power Automate admin center) that make HTTP requests based on app inputsAffected if Flows connected to Power Apps perform HTTP requests using URL parameters passed from the app
If Microsoft Power Apps is deployed and any app, connector, or flow can accept user-supplied URLs that trigger server-side requests, the environment is affected by CVE-2025-47733.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict allowlist validation for URLs provided by users, disable unnecessary URL protocols, and apply network segmentation to restrict outbound requests from the Power Apps service to internal resources.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47733 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-47733 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data