dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-69094

HIGH · 8.5 CVSS v3.1 Published 2026-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable Zero-click 7 weeks old

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
Subscriber SQL Injection in Unicamp <= 2.2.2 versions.

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

SQL injection vulnerability in the Unicamp WordPress plugin affecting versions 2.2.2 and below. The flaw allows authenticated users with Subscriber-level permissions to inject malicious SQL queries through unsanitized input parameters, potentially leading to data exfiltration or database compromise.

MitigationUpgrade Unicamp plugin to the latest version. If no patch is available, disable the plugin until a fix is released. Audit user roles and permissions as a temporary measure.

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 checks

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

  1. Confirm Unicamp plugin is installed
    Navigate to WordPress admin > Plugins and look for Unicamp plugin, or inspect the file /wp-content/plugins/unicamp/ for presence
    Affected if Unicamp plugin folder exists in the WordPress installation
  2. Check installed Unicamp version
    In WordPress admin > Plugins > Installed Plugins, find Unicamp and note the version number displayed, or read the version from /wp-content/plugins/unicamp/readme.txt or unicamp.php header
    Affected if Version is 2.2.2 or lower
  3. Verify WordPress user registration is enabled
    Go to WordPress admin > Settings > General > Membership and check if Anyone can register is checked
    Affected if User registration is enabled, allowing potential attacker to create a Subscriber account
  4. Confirm Subscriber role exists and is active
    Go to WordPress admin > Users > Roles and Permissions, or check if any user has Subscriber role assigned
    Affected if Subscriber role is available and users with this role can log in

You are affected if Unicamp plugin is installed with version 2.2.2 or lower AND user registration is enabled, allowing unauthenticated or any user to obtain Subscriber-level access.

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

Upgrade Unicamp plugin to the latest version. If no patch is available, disable the plugin until a fix is released. Audit user roles and permissions as a temporary measure.

Recommended fix Low confidence

Latest version of Unicamp (version higher than 2.2.2)

  1. Identify the current version of Unicamp theme or plugin installed on the site
  2. Check the official theme/plugin repository or vendor website for the latest available version
  3. Upgrade Unicamp to the latest version available, which should be higher than 2.2.2
  4. After upgrading, verify the SQL injection vulnerability is resolved by testing the subscriber functionality with parameterized queries or using a web application scanner
  5. Ensure all other WordPress core, themes, and plugins are also updated to their latest secure versions
Caveat Check vendor release notes for any breaking changes between current version and latest version before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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