CVE-2025-10748
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 · uneditedThe RapidResult plugin for WordPress is vulnerable to SQL Injection via the 's' parameter in all versions up to, and including, 1.2. This is due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers with contributor-level permissions and above to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
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 confidenceThe RapidResult WordPress plugin versions up to 1.2 contains a SQL injection vulnerability in the 's' parameter. The plugin fails to properly escape user-supplied input and does not use prepared statements, allowing authenticated users with contributor-level permissions or higher to inject arbitrary SQL queries and exfiltrate sensitive database content.
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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 RapidResult plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'RapidResult'. Alternatively, check the /wp-content/plugins/ directory for a folder named 'rapidresult' or check the plugin file headers in rapidresult.php for the version comment.Affected if The plugin is not installed or not present in the filesystem.
-
Check installed plugin versionIf the plugin is present, open the main plugin file (usually rapidresult.php) and locate the 'Version' header in the plugin comment block. Compare this version number against the affected range (versions 1.2 and below).Affected if The installed version is 1.2 or lower.
-
Confirm plugin is activeIn WordPress admin > Plugins, verify that RapidResult shows as 'Active'. Alternatively, query the wp_options table for option_name = 'active_plugins' and check if rapidresult/rapidresult.php is present in the serialized array.Affected if The plugin is active and the version is 1.2 or lower.
-
Verify user roles with contributor access existIn WordPress admin > Users, review the list of user accounts. Check if any users have the 'Contributor', 'Author', 'Editor', or 'Administrator' role, as these all have equal or higher permissions than Contributor.Affected if At least one user account with Contributor-level permissions or higher exists on the site.
A user is affected if the RapidResult plugin is installed, active, and running version 1.2 or lower, AND at least one user with Contributor-level permissions or higher exists on the site (allowing the SQL injection to be exploited).
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 the RapidResult plugin to version 1.3 or later. If no update is available, disable the plugin until a fix is released. Alternatively, modify the vulnerable code to use $wpdb->prepare() with parameterized queries for the 's' parameter.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10748 — 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-10748 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