LiveActive security incident?Get immediate response
CVE Record

CVE-2025-31611: WordPress Auto Post After Image Upload plugin <= 1.6 - Broken Access Control vulnerability

Missing Authorization vulnerability in Shaharia Azam Auto Post After Image Upload auto-post-after-image-upload allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Auto Post After Image Upload: from n/a through <= 1.6.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a broken access control issue in a WordPress plugin that automatically creates posts after image uploads. A logged-in low-privilege user may be able to perform an action they should not be authorized to perform. The known impact is limited to integrity, not data theft or service outage.

Executive priority

Treat this as a moderate-priority WordPress plugin exposure. It is not documented as actively exploited, but it can affect site content integrity where low-privilege accounts exist. Prioritize inventory, version confirmation, and vendor guidance review.

Technical view

CVE-2025-31611 is a CWE-862 Missing Authorization flaw in Shaharia Azam Auto Post After Image Upload through version 1.6. CVSS 3.1 is 4.3: network reachable, low complexity, low privileges required, no user interaction, unchanged scope, no confidentiality or availability impact, and low integrity impact.

Likely exposure

Exposure is limited to WordPress sites using Auto Post After Image Upload version 1.6 or earlier. Sites with multiple authenticated users, contributor-style roles, or untrusted accounts are more relevant. The bundle does not identify exact vulnerable functions, roles, or a fixed version.

Exploitation context

The source bundle does not show active exploitation, and the CVE is not listed as KEV. The vulnerability requires authenticated low-privilege access, so risk depends on whether the WordPress site allows non-admin users or compromised accounts.

Researcher notes

Evidence is limited to the CVE and Patchstack database reference. No exploit details, vulnerable endpoint, affected role mapping, or patched version is provided in the bundle. Validation should stay focused on asset presence, versioning, user-role exposure, and advisory updates.

Mitigation direction

  • Inventory WordPress sites for the Auto Post After Image Upload plugin.
  • Confirm whether installed versions are 1.6 or earlier.
  • Check Patchstack or vendor guidance for a fixed release or official workaround.
  • If no fix is available, assess disabling or replacing the plugin.
  • Review WordPress accounts and remove unnecessary low-privilege access.

Validation and detection

  • Check plugin inventory across production and staging WordPress instances.
  • Record installed plugin version and compare it with the affected range.
  • Review user roles with upload or content-management access.
  • Monitor WordPress logs for unexpected post or media-related changes.
  • Track vendor and Patchstack advisories for remediation updates.
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-31611 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-31611Attack 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
Shaharia AzamAuto Post After Image Uploadauto-post-after-image-upload, 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.