LiveActive security incident?Get immediate response
CVE Record

CVE-2023-46778: WordPress Auto Limit Posts Reloaded Plugin <= 2.5 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in TheFreeWindows Auto Limit Posts Reloaded plugin <= 2.5 versions.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This affects WordPress sites running TheFreeWindows Auto Limit Posts Reloaded plugin version 2.5 or earlier. The issue is CSRF: an attacker may abuse a logged-in user’s browser to trigger unwanted plugin-related actions. The public bundle rates impact high, but does not describe the exact vulnerable action or fixed release.

Executive priority

Treat as a priority inventory and remediation item for WordPress estates, not as confirmed emergency exploitation. The high CVSS score warrants prompt action, but urgency depends on whether the plugin is installed and whether vendor guidance identifies a fixed release.

Technical view

CVE-2023-46778 is a CWE-352 CSRF vulnerability in Auto Limit Posts Reloaded <= 2.5. The CVSS 3.1 vector is 8.8 high, network-accessible, low complexity, no attacker privileges, and user interaction required. Available sources do not provide endpoint details, proof of exploitation, or remediation version.

Likely exposure

Exposure is limited to WordPress installations with the Auto Limit Posts Reloaded plugin installed, especially version 2.5 or earlier. Sites without this plugin are not indicated as affected. The bundle’s affected metadata is sparse, so validate against actual plugin inventory.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. The attack class requires user interaction, typically a logged-in user being induced to visit attacker-controlled content. Exact impact depends on the plugin action affected, which is not detailed in the provided sources.

Researcher notes

Public detail is limited. Do not assume specific endpoints, actions, or exploitability beyond CSRF in Auto Limit Posts Reloaded <= 2.5. The CVSS vector claims high confidentiality, integrity, and availability impact, but the provided sources do not explain the mechanism.

Mitigation direction

  • Inventory WordPress sites for auto-limit-posts-reloaded installations.
  • Check Patchstack and vendor guidance for a fixed or safe version.
  • Update the plugin if a vendor-supported fixed version exists.
  • Disable or remove the plugin where it is unnecessary.
  • Restrict WordPress administrator access to trusted users and devices.

Validation and detection

  • Confirm whether Auto Limit Posts Reloaded is installed on each WordPress site.
  • Record installed plugin versions and flag version 2.5 or earlier.
  • Review Patchstack and CVE records for remediation updates.
  • Check recent WordPress admin activity for unexpected plugin-related changes.
  • Verify removal or update in production after change deployment.
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-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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-2023-46778 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
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

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

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
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2023-46778Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
TheFreeWindowsAuto Limit Posts Reloadedauto-limit-posts-reloaded, n/aunaffected
Weakness

CWE details

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

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.