CVE-2025-12850
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-12-05

Last updated on: 2025-12-08

Assigner: Wordfence

Description
The My auctions allegro plugin for WordPress is vulnerable to SQL Injection via the ‘auction_id’ parameter in all versions up to, and including, 3.6.32 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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-05
Last Modified
2025-12-08
Generated
2026-05-07
AI Q&A
2025-12-05
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
wordpress my_auctions_allegro 3.6.32
wordpress my_auctions_allegro 3.6.33
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

The vulnerability is an SQL Injection in the My auctions allegro plugin for WordPress, affecting all versions up to 3.6.32. It occurs via the 'auction_id' parameter because the plugin does not properly escape or prepare this user-supplied input. This allows unauthenticated attackers to inject additional SQL queries into existing database queries.


How can this vulnerability impact me? :

This vulnerability can allow attackers to extract sensitive information from the database without authentication, potentially leading to data breaches and exposure of confidential data.


What immediate steps should I take to mitigate this vulnerability?

The immediate mitigation step is to update the 'my-auctions-allegro-free-edition' WordPress plugin to version 3.6.33 or later, which includes the security fix for CVE-2025-12850. This update enhances input sanitization by adding 'sanitize_text_field()' before SQL escaping and uses prepared SQL statements to prevent injection. If updating immediately is not possible, consider disabling the plugin temporarily to prevent exploitation. Additionally, monitor and restrict access to the vulnerable endpoints and review web server logs for suspicious activity. [1]


How can this vulnerability be detected on my network or system? Can you suggest some commands?

You can detect this vulnerability by checking if your WordPress installation is running the 'my-auctions-allegro-free-edition' plugin version 3.6.32 or earlier. Since the vulnerability involves SQL Injection via the 'auction_id' parameter, you can monitor HTTP requests to the plugin's endpoints for suspicious or malformed 'auction_id' parameters that include SQL syntax. For example, using command-line tools like curl or grep, you might search web server logs for requests containing 'auction_id' with suspicious characters such as quotes or SQL keywords. Example command to search logs: grep -i 'auction_id=.*\(\|\'\|--\|union\)' /var/log/apache2/access.log. Additionally, scanning your WordPress plugins for version information can be done via WP-CLI: wp plugin list --format=json and check the version of 'my-auctions-allegro-free-edition'. [1]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart