CVE-2025-22728
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 AmentoTech Workreap (theme's plugin) workreap allows SQL Injection.This issue affects Workreap (theme's plugin): from n/a through <= 3.3.6.
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 Workreap WordPress theme plugin allows attackers to inject malicious SQL commands through unsanitized user input. With a CVSS of 8.5, this high-severity flaw could enable unauthorized data access, data manipulation, or potentially remote code execution depending on database configurations.
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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify Workreap installation and versionLocate the Workreap theme or plugin in your WordPress installation. Check the theme directory (wp-content/themes/workreap) or plugin directory for workreap-related folders. Open the main style.css file or primary plugin PHP file to find the declared version number.Affected if Workreap theme or plugin is installed and the version matches the affected unpatched versions (compare to vendor advisory for exact range)
-
Locate SQL query code vulnerable to injectionSearch the Workreap codebase for direct SQL query execution functions such as $wpdb->query(), $wpdb->prepare() used without proper parameter binding, or raw SQL concatenation. Focus on files handling user-submitted data like search, filter, form submission, or query parameter handlers.Affected if Unsanitized SQL queries exist that accept user input directly without using prepared statements or proper escaping
-
Identify user input entry pointsExamine PHP files that process REQUEST, GET, POST, or COOKIE parameters and pass them to SQL queries. Common entry points include search forms, category filters, sorting parameters, ID parameters in URLs, and AJAX handlers.Affected if User-supplied parameters are being used in SQL queries without validation or prepared statement parameter binding
-
Verify lack of input sanitizationReview the identified SQL query code paths to confirm that user input is not being sanitized via esc_sql(), sanitize_text_field(), or similar WordPress sanitization functions before being included in database queries.Affected if User input flows directly into SQL queries without sanitization functions or prepared statement placeholders
If Workreap is installed with an unpatched version and your codebase contains SQL queries that accept unsanitized user input, the environment is likely affected by this vulnerability.
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 Workreap to the latest patched version. If no patch is available, audit the codebase for unsanitized SQL queries and implement prepared statements or proper input validation/escaping.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22728 — 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-22728 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