LiveActive security incident?Get immediate response
CVE Record

CVE-2025-31530: WordPress Google SEO Pressor Snippet plugin <= 2.0 - Broken Access Control vulnerability

Missing Authorization vulnerability in Smackcoders Inc., Google SEO Pressor Snippet google-seo-author-snippets allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Google SEO Pressor Snippet: from n/a through <= 2.0.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-31530 is a broken access control issue in the WordPress Google SEO Pressor Snippet plugin through version 2.0. A logged-in user may be able to perform an action that should require stronger authorization. The reported impact is limited to integrity, with no stated confidentiality or availability impact.

Executive priority

Treat as a moderate-priority WordPress hygiene issue. It is not described as remotely exploitable without login, but affected public sites with many user accounts should remediate promptly to reduce unauthorized content or SEO-related changes.

Technical view

The CVE describes missing authorization, CWE-862, in Smackcoders Google SEO Pressor Snippet, package google-seo-author-snippets, through version 2.0. CVSS 3.1 is 4.3: network reachable, low complexity, low privileges required, no user interaction, unchanged scope, low integrity impact only.

Likely exposure

Exposure is likely limited to WordPress sites that installed Google SEO Pressor Snippet version 2.0 or earlier and allow authenticated users below the intended privilege level. Sites without this plugin are not affected based on the provided sources.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. The vulnerability requires an authenticated user, which lowers broad internet risk but still matters on sites with many contributors, subscribers, or weak account governance.

Researcher notes

Evidence is limited to the CVE metadata and Patchstack reference in the bundle. No exploit details, patch version, or active exploitation source is provided. Validation should focus on installed plugin presence, version, and authorization boundaries for plugin actions.

Mitigation direction

  • Inventory WordPress sites for google-seo-author-snippets through version 2.0.
  • Check vendor, WordPress plugin, or Patchstack guidance for a fixed version or retirement notice.
  • Disable or remove the plugin where it is not business-critical.
  • Limit low-privilege WordPress accounts until remediation is confirmed.
  • Review plugin-related changes for unexpected SEO snippet or author metadata modifications.

Validation and detection

  • Confirm whether the plugin slug google-seo-author-snippets is installed.
  • Record the installed plugin version and flag version 2.0 or earlier.
  • Review WordPress roles with authenticated access on affected sites.
  • Verify sensitive plugin actions require the intended capability in a controlled environment.
  • Check audit logs for unexpected plugin configuration or content changes.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-31530 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2025-31530Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Smackcoders Inc.,Google SEO Pressor Snippetgoogle-seo-author-snippets, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.