WebinarpressWordPress extension
CVE-2025-47635
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 WPWebinarSystem WebinarPress wp-webinarsystem allows Server Side Request Forgery.This issue affects WebinarPress: from n/a through <= 1.33.28.
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 · high confidenceServer-Side Request Forgery (SSRF) vulnerability in the WPWebinarSystem WebinarPress WordPress plugin (wp-webinarsystem) allows remote unauthenticated attackers to make the server perform requests to arbitrary URLs. The CVSS 9.8 indicates the flaw is exploitable over the network without authentication and can lead to complete compromise of confidentiality, integrity, and availability.
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 data
WebinarpressWordPress extension
<= 1.33.27CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 WebinarPress plugin is installedCheck the WordPress plugins directory for the wp-webinarsystem folder, typically at wp-content/plugins/wp-webinarsystem/Affected if The plugin folder wp-webinarsystem exists on the server
-
Determine the installed version of WebinarPressOpen the main plugin file (wp-webinarsystem.php or similar) in the plugin directory and look for the Version header in the plugin comments, or check the readme.txt file for the version numberAffected if The version listed is 1.33.27 or lower (any version <= 1.33.27)
-
Inspect plugin files for URL-handling functionsSearch the plugin directory for code that performs HTTP requests (e.g., wp_remote_get, wp_remote_post, file_get_contents with URLs, curl functions) and accepts user-controlled URLs without proper validationAffected if The plugin contains code that makes outgoing HTTP requests based on input without validating the target URL
-
Check for vulnerable parameters in plugin endpointsReview AJAX handlers or form processing files in the plugin for parameters that accept full URLs (such as callback_url, redirect_url, or similar) and are used in server-side request functions without sanitizationAffected if The plugin accepts URL parameters and uses them in server-side requests without allowlist validation
You are affected if the WebinarPress plugin is installed with any version <= 1.33.27 and the plugin contains functionality that accepts and processes arbitrary URLs from external input.
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 dataUpdate to the latest version of WebinarPress if a patch is available; otherwise, restrict outgoing network connections from the web server and implement URL allowlist validation in the plugin to prevent the server from making arbitrary requests to internal resources or external systems.
Fix this in Webinarpress
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47635 — 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-47635 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