LiveActive security incident?Get immediate response
CVE Record

CVE-2023-46625: WordPress Autolinks Manager Plugin <= 1.10.04 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in DAEXT Autolinks Manager plugin <= 1.10.04 versions.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a medium-severity CSRF issue in the WordPress DAEXT Autolinks Manager plugin through version 1.10.04. An attacker would need a user to interact with malicious content, but successful abuse could make unauthorized changes related to the plugin. The provided sources do not show data theft, service outage, or active exploitation.

Executive priority

Treat as a routine but timely WordPress plugin remediation. It is not currently evidenced as exploited, but exposed public websites with vulnerable plugin versions should be fixed during the next normal maintenance window.

Technical view

CVE-2023-46625 is CWE-352 affecting DAEXT Autolinks Manager <= 1.10.04. CVSS 3.1 is 4.3 with network attack vector, low complexity, no attacker privileges, required user interaction, unchanged scope, and low integrity impact only. The bundle describes multiple CSRF exposure but does not include endpoint-level detail or a confirmed fixed version.

Likely exposure

Exposure is limited to WordPress sites running DAEXT Autolinks Manager version 1.10.04 or older. Risk depends on whether users with access to affected plugin functions can be induced to interact with attacker-controlled content while authenticated.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation. The CVSS vector indicates exploitation requires user interaction and produces limited integrity impact, with no stated confidentiality or availability impact.

Researcher notes

Evidence is incomplete beyond the CVE metadata and Patchstack entry. Do not assume endpoint names, exploitability details, or a fixed version from the provided bundle. Validation should focus on version presence, vendor advisory review, and unexpected plugin configuration changes.

Mitigation direction

  • Inventory WordPress sites for DAEXT Autolinks Manager installations.
  • Flag plugin versions 1.10.04 or older as vulnerable.
  • Check DAEXT or Patchstack guidance for an official fixed version.
  • Update the plugin when an official fixed release is confirmed.
  • Disable the plugin temporarily where it is not business-critical.

Validation and detection

  • Confirm installed plugin name and version on each WordPress site.
  • Review administrative logs for unexpected Autolinks Manager configuration changes.
  • Verify whether vendor guidance identifies a patched version.
  • After updating or disabling, confirm the vulnerable version is no longer present.
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-46625 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:N/UI:R/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:N/UI:R/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-2023-46625Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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
DAEXTAutolinks Managerdaext-autolinks-manager, 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.