CVE-2025-30998
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 Rico Macchi WP Links Page wp-links-page allows SQL Injection.This issue affects WP Links Page: from n/a through <= 4.9.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 · high confidenceSQL Injection vulnerability in the WP Links Page WordPress plugin allows attackers to inject malicious SQL commands via unsanitized user input. The improper neutralization of special elements in SQL queries enables database compromise, potentially leading to unauthorized data access, modification, or disclosure.
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.
-
Verify WP Links Page plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'wp-links-page' or 'wp-links-page-master', or inspect the plugin list in the WordPress admin dashboard under Plugins > Installed PluginsAffected if The plugin folder exists in the WordPress installation
-
Determine installed plugin versionLocate the main plugin file (typically wp-links-page.php) and read the 'Version' header in the plugin file comment block, or view the version in WordPress admin under Plugins > Installed PluginsAffected if The reported version is 4.9.6 or lower (the vulnerability affects all versions up to and including 4.9.6)
-
Identify if link submission input fields are accessibleNavigate to the plugin's front-end link submission page (usually at /links/submit/ or similar URL pattern used by the plugin) and check if user input forms for adding/editing links are publicly accessibleAffected if The plugin provides a publicly accessible form that accepts user input for link data (name, URL, description, category, etc.) without authentication requirements
-
Inspect for SQL query execution in plugin codeExamine the plugin's PHP files (particularly submission handler files) for direct SQL queries using $wpdb->prepare, mysql_* functions, or unsanitized variables in WHERE/INSERT/UPDATE clausesAffected if The plugin code contains SQL queries that incorporate user-supplied input without using prepared statements or proper escaping (looking for $_POST, $_GET, or $_REQUEST variables used directly in queries)
You are affected if the WP Links Page plugin is installed with version 4.9.6 or lower and includes publicly accessible input fields for link submissions that lack proper SQL input sanitization.
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 dataUpgrade WP Links Page to the latest version that addresses this vulnerability, or if no patch is available, implement input validation and parameterized queries using WordPress $wpdb->prepare() for all database interactions.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30998 — 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-30998 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