CVE-2025-30525
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in ProfitShare.ro WP Profitshare wp-profitshare allows SQL Injection.This issue affects WP Profitshare: from n/a through <= 1.4.9.
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 confidenceSQL injection vulnerability in the WP Profitshare WordPress plugin allows attackers to inject malicious SQL commands through unsanitized input. The vulnerability exists in the plugin's database queries, potentially allowing unauthorized access to or manipulation of the site's database. This affects all versions up to and including 1.4.9.
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/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.
-
Locate WP Profitshare plugin installationCheck your WordPress site's wp-content/plugins/ directory for a folder named 'profitshare' or 'wp-profitshare'. Alternatively, log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins to verify the plugin is present.Affected if The plugin folder exists in wp-content/plugins/ or the plugin appears in the WordPress admin plugin list.
-
Determine installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and locate WP Profitshare. The version number is displayed below the plugin name. Alternatively, open the main plugin file (usually profitshare.php or wp-profitshare.php in the plugin folder) and search for a 'Version:' comment or $version variable in the plugin header.Affected if The displayed version is 1.4.9 or any lower version number.
-
Verify plugin is activeIn WordPress admin under Plugins > Installed Plugins, confirm the WP Profitshare plugin shows as 'Active' (not just installed but not activated).Affected if The plugin status shows as Active.
-
Check for vulnerable query code (optional manual inspection)Examine the main plugin PHP files for direct SQL queries using $wpdb->prepare without proper sanitization, or queries built by string concatenation without escaping. Look for patterns like $wpdb->query($sql) or $wpdb->get_results($sql) where $sql contains unsanitized $_POST, $_GET, or $_REQUEST variables.Affected if Raw SQL queries accept user input without using $wpdb->prepare() or esc_sql() functions.
You are affected if the WP Profitshare plugin is installed, active, and the version is 1.4.9 or lower.
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 WP Profitshare to the latest version once available, or implement input validation and parameterized queries in the plugin code to neutralize the SQL injection vectors. Consider disabling the plugin until a patch is applied if the update is not yet available.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30525 — 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-30525 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