dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-49455

CRITICAL · 9.3 CVSS v3.1 Published 2025-06-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in ClickandPledge WordPress-WPJobBoard click-pledge-wpjobboard allows Blind SQL Injection.This issue affects WordPress-WPJobBoard: from n/a through <= 25.07010000-WP6.8.1-JB5.11.5.

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 confidence

A blind SQL injection vulnerability exists in the ClickandPledge WordPress WPJobBoard plugin (click-pledge-wpjobboard) due to improper neutralization of special elements in SQL commands. Attackers can inject malicious SQL queries through unsanitized user input, potentially allowing unauthorized data access or manipulation of the database.

MitigationApply vendor-supplied patch or update to the latest version of the WPJobBoard plugin when available. As an interim measure, disable the ClickandPledge integration until patched, and review WAF rules for SQL injection detection.

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
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm plugin installation
    Check for the presence of the wp-pledge-wpjobboard plugin in your WordPress installation under wp-content/plugins/ or via the WordPress admin plugins page
    Affected if The ClickandPledge WPJobBoard plugin (wp-pledge-wpjobboard) is installed and active
  2. Identify installed version
    Locate the main plugin file (typically wp-pledge-wpjobboard.php) and read the version header, or use wp-cli: wp plugin get wp-pledge-wpjobboard --field=version
    Affected if The installed version is 25.07010000-WP6.8.1-JB5.11.5 or any earlier version (the vulnerability affects versions through this version)
  3. Verify exposure to unauthenticated users
    Confirm the plugin is accessible to unauthenticated visitors on your site. This is the default state for WordPress plugins unless specific access controls have been applied
    Affected if The plugin is active and its functionality is accessible to unauthenticated (logged-out) users, which is the default configuration
  4. Identify SQL query entry points
    Review plugin source code for direct database queries using $wpdb->prepare or similar that incorporate user input without proper sanitization. Focus on files handling form submissions, search parameters, or URL query variables
    Affected if The plugin contains dynamic SQL query construction that uses unsanitized $_GET, $_POST, or $_REQUEST parameters
  5. Check for blind SQL injection indicators
    Analyze the plugin for SQL query patterns that accept user input (such as search fields, filters, or ID parameters) and are executed without parameterized queries. Look for direct string concatenation in $wpdb->query or $wpdb->prepare calls
    Affected if SQL queries in the plugin use string concatenation with user-supplied input instead of prepared statement placeholders (%s, %d)

If the wp-pledge-wpjobboard plugin is installed at version 25.07010000-WP6.8.1-JB5.11.5 or earlier and is accessible to unauthenticated users, your environment is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patch or update to the latest version of the WPJobBoard plugin when available. As an interim measure, disable the ClickandPledge integration until patched, and review WAF rules for SQL injection detection.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49455 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-49455 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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