dbcve.org
Ultimate Wordpress Auction PluginWordPress extension · Auctionplugin

CVE-2025-4204

HIGH · 7.5 CVSS v3.1 Published 2025-05-02
Fix available
A fix is available. Upgrade to 1.5.3 or later.
See remediation →
84/100
Remediation priority · High
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
The Ultimate Auction Pro plugin for WordPress is vulnerable to SQL Injection via the ‘auction_id’ parameter in all versions up to, and including, 1.5.2 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers 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 confidence

The Ultimate Auction Pro WordPress plugin versions up to 1.5.2 contains a SQL injection vulnerability in the 'auction_id' parameter. The plugin fails to properly escape user-supplied input before incorporating it into SQL queries and does not use prepared statements, allowing unauthenticated attackers to inject arbitrary SQL code and potentially extract sensitive data from the database.

MitigationUpdate the Ultimate Auction Pro plugin to version 1.5.3 or later which includes proper input sanitization and prepared statement usage. Until the patch can be applied, consider restricting access to the affected endpoint at the web server level.

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
Ultimate Wordpress Auction PluginWordPress extension
Affected:< 1.5.3

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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

  1. Confirm plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for the Ultimate Auction Pro plugin folder. Look for the main plugin PHP file and inspect the plugin header comment for the version number.
    Affected if The plugin folder exists and contains the Ultimate Auction Pro plugin files.
  2. Determine installed version
    Read the plugin version from the main PHP file header (e.g., Version: x.x.x) or from the plugin's readme.txt file. Compare this version to 1.5.3.
    Affected if Installed version is lower than 1.5.3.
  3. Verify vulnerable parameter exists
    Search the plugin source code for usage of the 'auction_id' parameter in SQL queries. Look for direct insertion of this parameter into database queries without prepared statements or proper escaping.
    Affected if The auction_id parameter is used in SQL queries without prepared statement formatting (e.g., no $wpdb->prepare(), no parameterized queries).
  4. Check if plugin is active
    In the WordPress admin dashboard, go to Plugins > Installed Plugins and verify whether the Ultimate Auction Pro plugin is activated.
    Affected if The plugin is installed and active on the WordPress site.

If the Ultimate Auction Pro plugin is installed with a version below 1.5.3 and the auction_id parameter is used in unauthenticated SQL queries, the environment is vulnerable to CVE-2025-4204.

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.

dbcve · scoped
Upgrade available Upgrade to 1.5.3 or later
Fixed in 1.5.3
Interim mitigation

Update the Ultimate Auction Pro plugin to version 1.5.3 or later which includes proper input sanitization and prepared statement usage. Until the patch can be applied, consider restricting access to the affected endpoint at the web server level.

Recommended fix High confidence

Ultimate WordPress Auction Plugin version 1.5.3

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Ultimate WordPress Auction Plugin (or Ultimate Auction Pro)
  4. Check if an update to version 1.5.3 or later is available
  5. If an update is available, click 'Update Now' to upgrade to version 1.5.3
  6. Alternatively, navigate to Dashboard > Updates and select the plugin to update
  7. After updating, verify the plugin version shows 1.5.3 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ultimate Wordpress Auction Plugin Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-4204 — 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-4204 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