LiveActive security incident?Get immediate response
CVE Record

CVE-2024-25927: WordPress postMash – custom post order Plugin <= 1.2.0 is vulnerable to SQL Injection

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Joel Starnes postMash – custom post order.This issue affects postMash – custom post order: from n/a through 1.2.0.

CriticalCVSS 9.3Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2024-25927 is a critical SQL injection issue in the WordPress postMash – custom post order plugin through version 1.2.0. A vulnerable public WordPress site could expose database data or suffer limited availability impact. The provided sources do not confirm active exploitation or name a fixed version.

Executive priority

Treat this as urgent for any internet-facing WordPress site using postMash. The business risk is potential database exposure from an unauthenticated flaw. Prioritize inventory first, then remove, disable, or update based on current vendor guidance.

Technical view

The issue is CWE-89 SQL injection in Joel Starnes postMash – custom post order. The CVSS 3.1 vector is network-accessible, low complexity, unauthenticated, and requires no user interaction, with high confidentiality impact, no integrity impact, and low availability impact.

Likely exposure

Exposure is limited to WordPress installations running postMash – custom post order through version 1.2.0. Publicly reachable WordPress sites using this plugin should be prioritized because the CVSS vector indicates unauthenticated network attack surface.

Exploitation context

The source bundle marks KEV as false, so active exploitation is not established here. Patchstack and CVE sources identify the vulnerability class and affected plugin version range, but the supplied evidence does not include exploit prevalence, proof-of-concept status, or a named patch.

Researcher notes

Do not assume all WordPress sites are affected; exposure depends on this specific plugin. The sources provide severity, affected range, and vulnerability type, but not endpoint details, exploit maturity, or a confirmed fixed release.

Mitigation direction

  • Inventory WordPress sites for the postMash plugin and exact installed version.
  • Check vendor, WordPress.org, and Patchstack guidance for a fixed or recommended action.
  • Disable or remove the plugin where no supported safe version is available.
  • Increase monitoring for database errors and suspicious unauthenticated requests.
  • Back up affected sites before plugin removal or remediation work.

Validation and detection

  • Confirm whether each WordPress site has postMash installed and enabled.
  • Record plugin versions and flag any installation through version 1.2.0.
  • Review CVE and Patchstack entries for updated remediation or exploitation notes.
  • Check web, WAF, and database logs for unusual SQL errors or probing.
  • Validate remediation by confirming the vulnerable plugin is removed, disabled, or updated per vendor guidance.
Prepared
Confidence
high
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-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-25927 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
Critical
CVSS
9.3 (3.1)
Known Exploited
No
Published

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

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
9.3CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L3.94.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.3Critical
CVSS 3.1 vector shape for CVE-2024-25927Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
Joel StarnespostMash – custom post orderpostmash, n/aunaffected
Weakness

CWE details

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

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.