CVE-2025-67961
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) vulnerability in Marco van Wieren WPO365 wpo365-login allows Server Side Request Forgery.This issue affects WPO365: from n/a through <= 40.0.
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 exists in the WPO365 login plugin (versions up to 40.0). The vulnerability allows an attacker to induce the server to make arbitrary HTTP requests to internal or external resources by manipulating input parameters used in server-side requests, potentially accessing internal services, cloud metadata, or performing attacks against internal infrastructure.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/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.
-
Verify WPO365 plugin versionLog into WordPress admin, navigate to Plugins > Installed Plugins, locate WPO365 | Login with Microsoft, and read the version number displayed under the plugin nameAffected if The installed version is 40.0 or lower (any version up to and including 40.0)
-
Confirm WPO365 login functionality is activeNavigate to WPO365 plugin settings and verify that any Microsoft/Office 365 login feature is enabled or configuredAffected if The login feature that makes server-side requests is active and accessible to users
-
Identify URL-handling parameters in login flowReview the WPO365 configuration for any fields that accept URLs or endpoints, such as redirect URIs, callback URLs, or custom endpoint definitionsAffected if URL-related parameters exist in the login configuration that could be manipulated
-
Test for SSRF injection pointsIf you have testing capability, examine whether the login functionality allows arbitrary URL input that the server will request (check for fields accepting full URLs, domain names, or IP addresses)Affected if User-supplied or configurable URLs can be passed to server-side request functions without validation
You are affected if WPO365 version 40.0 or lower is installed AND the login feature handling external requests is enabled, allowing manipulation of URL parameters.
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.
dbcve · scopedUpgrade WPO365 to a version beyond 40.0 that contains the SSRF fix. If no patch is available, review and restrict all URL-related parameters in the login functionality to an explicit allow-list of permitted domains or IP addresses.
WPO365 version > 40.0
- 1. Check the WordPress admin panel for plugin updates under Plugins > WPO365
- 2. If no update is available, contact the vendor (Marco van Wieren) directly for the patched version
- 3. Verify the new version is greater than 40.0 before updating
- 4. Backup the site before applying any plugin update
- 5. Test the update in a staging environment if possible
Generated from the published advisory — verify against the referenced sources before acting.
- 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-67961 — 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-67961 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