CVE-2025-30528
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in wpshopee Awesome Logos awesome-logos allows SQL Injection.This issue affects Awesome Logos: from n/a through <= 1.2.
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 confidenceA combined Cross-Site Request Forgery (CSRF) and SQL Injection vulnerability exists in the Awesome Logos WordPress plugin (versions up to and including 1.2). The CVSS score of 9.3 indicates critical severity, likely due to the SQL Injection component allowing unauthenticated attackers to manipulate database queries through crafted requests.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Awesome Logos plugin is installedNavigate to WordPress admin dashboard > Plugins and check if 'Awesome Logos' appears in the installed plugins list, or inspect the wp-content/plugins/ directory for an awesome-logos folderAffected if The plugin folder 'awesome-logos' exists in the plugins directory and the plugin is active
-
Check installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins > Awesome Logos and view the version number displayed, or open the main plugin PHP file and check the 'Version:' header in the plugin comment blockAffected if The displayed version is 1.2 or any version number lower than 1.2
-
Identify vulnerable code patternsLocate PHP files within the awesome-logos plugin folder and search for SQL query functions (such as $wpdb->query, $wpdb->get_results, or direct $wpdb->prepare calls) that handle user-supplied input from $_POST, $_GET, or $_REQUEST without proper sanitizationAffected if Database query code processes user input without using WordPress nonces for CSRF protection and without $wpdb->prepare() for SQL parameterization
-
Check for nonce verification on state-changing actionsReview plugin PHP files that handle form submissions, AJAX requests, or URL parameters that modify data (such as settings updates, database operations, or plugin configuration changes) and verify if wp_verify_nonce or check_admin_referer is calledAffected if State-changing operations (POST/GET requests that modify data) lack nonce verification checks, leaving the plugin vulnerable to CSRF attacks that can trigger SQL injection
A user is affected if the Awesome Logos plugin is installed and active with version 1.2 or lower, and the plugin code contains SQL queries that handle user input without WordPress nonce validation and without $wpdb->prepare() parameterization.
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 the Awesome Logos plugin to the latest version if available, or remove the plugin until a patched version is released. Apply WordPress nonces to all state-changing operations and use parameterized queries (prepare()) for all database interactions.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30528 — 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-30528 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