CVE-2025-0853
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 · uneditedThe PGS Core plugin for WordPress is vulnerable to SQL Injection via the 'event' parameter in the 'save_header_builder' function in all versions up to, and including, 5.8.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
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 confidenceThe PGS Core WordPress plugin is vulnerable to unauthenticated SQL injection in the save_header_builder function via the event parameter. Insufficient input escaping and missing prepared statements allow attackers to inject arbitrary SQL queries and extract sensitive database information.
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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Locate the PGS Core plugin installationAccess your WordPress site via FTP or file manager and navigate to /wp-content/plugins/pgs-core/. Check for a readme.txt or the main plugin file to identify the installed version number.Affected if The plugin is present in the /wp-content/plugins/ directory with a version lower than 5.8.1.
-
Verify the plugin version via WordPress adminLog in to WordPress admin, go to Plugins > Installed Plugins. Find PGS Core in the list and note the version number displayed under the plugin name.Affected if The displayed version is lower than 5.8.1.
-
Identify the vulnerable save_header_builder functionExamine the plugin files (typically in the /includes/ or /functions/ folder within the plugin directory) for a function named save_header_builder that processes an 'event' parameter without proper escaping or prepared statements.Affected if The function exists and processes the event parameter directly in SQL queries without escaping or prepared statements.
-
Check if the vulnerable endpoint is publicly accessibleTest if the WordPress REST API or AJAX endpoint that calls save_header_builder is accessible without authentication. Look for routes like /wp-json/pgs-core/v1/ or /wp-admin/admin-ajax.php?action=pgs_core_save_header.Affected if The endpoint responds without requiring authentication (anonymous access allowed).
-
Review WordPress access logs for SQL injection attemptsSearch your server access logs for requests to the save_header_builder endpoint containing suspicious SQL syntax in the 'event' parameter, such as UNION SELECT, SLEEP(), or boolean-based payloads.Affected if Log entries show malicious SQL patterns in the event parameter targeting this endpoint.
You are affected if the PGS Core plugin is installed with a version lower than 5.8.1 and the save_header_builder endpoint is accessible without authentication.
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 PGS Core plugin to version 5.8.1 or later. If no update is available, disable the plugin immediately to prevent exploitation.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0853 — 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-0853 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