dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-52722

CRITICAL · 9.3 CVSS v3.1 Published 2025-06-27
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 JoinWebs Classiera classiera allows SQL Injection.This issue affects Classiera: from n/a through <= 4.0.34.

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

SQL Injection vulnerability in JoinWebs Classiera theme allows attackers to inject malicious SQL commands via unsanitized input parameters. This critical pre-authentication flaw can lead to unauthorized database access, data exfiltration, or complete system compromise.

MitigationImplement parameterized queries/prepared statements for all database interactions and sanitize user-supplied input. If a patched version exists, upgrade immediately; otherwise, restrict access to affected endpoints until remediation is complete.

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. Identify if Classiera theme is installed
    Locate the Classiera theme files in the web application's directory structure. Check common theme locations such as /wp-content/themes/classiera/ for WordPress implementations, or look for classiera-related directories, classiera.php, or classiera-related class files in the application.
    Affected if The JoinWebs Classiera theme files are present in the environment
  2. Determine Classiera theme version
    Examine the theme's version information typically found in style.css headers, version.php, or a theme.json/config file. Compare your installed version against any known affected version ranges for this CVE.
    Affected if The installed version falls within the vulnerable version range for this CVE
  3. Review database query code for SQL injection flaws
    Search theme PHP files for direct SQL query construction, particularly in functions handling search, filtering, user submissions, or any code that incorporates $_GET, $_POST, or $_REQUEST parameters into database queries. Look for patterns like mysql_query, $wpdb->prepare without proper placeholders, or string concatenation in SQL statements.
    Affected if Code constructs SQL queries by concatenating or interpolating user input directly without using prepared statements or parameterized queries
  4. Identify unsanitized input parameters in SQL contexts
    Trace user-controlled parameters (from URL query strings, form inputs, or cookies) as they flow into database operations. Check if these parameters are validated, escaped, or cast to appropriate types before being used in SQL statements.
    Affected if User-supplied parameters from HTTP requests are used in SQL queries without sanitization, escaping, or type casting
  5. Verify vulnerability is reachable without authentication
    Confirm the vulnerable code executes in code paths accessible to unauthenticated users. Check if the affected functionality (search, filters, listings, etc.) can be accessed before any login or session check.
    Affected if The vulnerable SQL injection points are accessible to unauthenticated users (pre-authentication)

If the Classiera theme is present, its version is within the affected range, and SQL queries incorporate unsanitized user input in accessible (pre-auth) code paths, the environment is affected by CVE-2025-52722.

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

Implement parameterized queries/prepared statements for all database interactions and sanitize user-supplied input. If a patched version exists, upgrade immediately; otherwise, restrict access to affected endpoints until remediation is complete.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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