CVE-2025-22582
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Scott Nelle Uptime Robot uptime-robot allows Stored XSS.This issue affects Uptime Robot: from n/a through <= 0.1.3.
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 confidenceCSRF vulnerability in Uptime Robot <= 0.1.3 allows attackers to perform actions on behalf of authenticated users, leading to Stored XSS where malicious scripts are persistently embedded in the application.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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 Uptime Robot plugin versionAccess the plugin/theme management interface or check the plugin's main PHP file header for the 'Version' comment. For WordPress, this is typically in wp-content/plugins/uptime-robot/*.php or similar path. For other platforms, locate the package metadata.Affected if The installed version number is 0.1.3 or lower (e.g., 0.1.3, 0.1.2, 0.1.1, 0.1.0)
-
Verify absence of anti-CSRF tokens in formsInspect the HTML source of state-changing forms (e.g., monitor configuration, alert settings, dashboard controls) and look for hidden input fields containing tokens (such as 'csrf_token', '_wpnonce', 'nonce', or 'token') submitted with POST requests.Affected if State-changing forms lack any anti-CSRF token field or validation mechanism
-
Test for CSRF vulnerabilityCreate a malicious HTML page that submits a crafted POST request to a state-changing endpoint (e.g., adding/editing a monitor, changing settings) without the victim's knowledge, then attempt to trigger it while authenticated as a user.Affected if The application processes the state-changing request without validating the origin or requiring authentication proof
-
Check for stored XSS injection pointsReview the application's input fields (monitor names, URLs, alert contacts, custom fields) and inspect how submitted data is reflected in the dashboard or stored in the database. Look for unencoded output in HTML contexts.Affected if User-supplied input in monitor configuration or alert settings is stored and displayed without proper output encoding, allowing script injection
Your environment is affected if the installed Uptime Robot version is 0.1.3 or lower AND state-changing operations lack CSRF protection AND user input is not properly encoded, allowing stored XSS.
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 anti-CSRF tokens on state-changing operations and apply proper input validation with output encoding to prevent XSS injection; upgrade to any patched version if available.
- 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-22582 — 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-22582 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