Vulnerability report

Trusted Third Party Report Confirmed Confidence In CISA KEV

CVE-2025-24989

Microsoft Power Pages Elevation of Privilege Vulnerability

Microsoft Power Pages · -

Severity
CVSS 8.2 · High
Confidence
Confirmed
Exploit status
Trusted Third Party Report
EPSS
1.6%
First observed
—
Last observed
—

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2025-24989 is an unauthenticated Microsoft Power Pages Elevation of Privilege Vulnerability.

Have exploitation attempts been observed?

Yes. Exploitation attempts have been reported for this vulnerability. Previdian lists it as a known exploited vulnerability. Listed in CISA KEV. Confidence is confirmed.

Who is affected?

Microsoft Power Pages -.

What should we do?

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

Overview

Microsoft Power Pages Elevation of Privilege Vulnerability

An improper access control vulnerability in Power Pages allows an unauthorized attacker to elevate privileges over a network potentially bypassing the user registration control. This vulnerability has already been mitigated in the service and all affected customers have been notified. This update addressed the registration control bypass.

Affected customers have been given instructions on reviewing their sites for potential exploitation and clean up methods. If you've not been notified this vulnerability does not affect you.

Microsoft Affected
Microsoft Power Pages
-
View vendor advisory (opens in new tab)
Published
19 Feb 2025
Exploitation Attempts Reported
21 Feb 2025
Attack vector
Remote
Complexity
Low
Privileges
None
User interaction
None

Tags

microsoft cisa windows

CVE References

Exploitation evidence

Evidence of exploitation attempts

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploitation Attempts Observed in the Wild

CISA

Recorded 21 Feb 2025

A trusted third party reported exploitation attempts.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the Previdian Pro API.

Learn about Pro API access
Source Added
CISA First 2025-02-21 00:00 UTC

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Scanner coverage

No scanner integrations recorded yet.

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

No detection artifacts or sensor request patterns are available for this CVE yet.

Check back as sensor telemetry and scanner integrations are updated.

Risk and context

Severity, weaknesses, and research context

CVSS v3.1

8.2 High

Potential damage if exploited. Separate from whether attackers are using it.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N/E:U/RL:O/RC:C

EPSS

1.6%

Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.

Timeline

From disclosure to observed exploitation attempts

  1. 00:00 UTC

    Added to CISA KEV

    Listed in the CISA Known Exploited Vulnerabilities catalog

  2. 22:18 UTC

    CVE published

    Vulnerability disclosed publicly

  3. 15:14 UTC

    CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2025-24989

Sample API response
{
  "cve_id": "CVE-2025-24989",
  "confidence": "Confirmed",
  "cvss_score": 8.2,
  "cvss_estimated": false,
  "epss_score": 0.01622,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": false
  },
  "sensor_telemetry": { "attempts": 0, "sensors": 0 }
}