Security readout for executives and security teams
Plain-English summary
DirectoryPress for WordPress has a CSRF flaw affecting versions through 3.6.22. A logged-in site administrator could be tricked into causing unintended changes by visiting malicious content. The sources do not identify stolen data impact or active exploitation.
Executive priority
Treat as a moderate WordPress plugin risk. Prioritize inventory and update planning, especially for public or business-critical sites, but do not treat it as emergency exploitation without new evidence.
Technical view
CVE-2025-32249 is CWE-352 in Designinvento DirectoryPress. CVSS 3.1 is 5.4 with network attack vector, low complexity, no attacker privileges, and required user interaction. Reported impact is low integrity and low availability, with no confidentiality impact.
Likely exposure
Exposure is limited to WordPress sites using the DirectoryPress plugin at affected versions, reported as through 3.6.22. Sites without this plugin are not exposed based on the sources.
Exploitation context
No KEV listing is present, and the provided sources do not claim active exploitation. Successful abuse requires a victim interaction while authenticated to the affected WordPress site.
Researcher notes
The CVE description states affected versions through 3.6.22, while the Patchstack reference URL mentions 3.6.19. Scope should be verified against current vendor or Patchstack data before final asset decisions.
Mitigation direction
- Inventory WordPress sites for the DirectoryPress plugin and installed version.
- Check vendor or Patchstack guidance for fixed versions or official workarounds.
- Update DirectoryPress when a vendor-supported fixed release is confirmed.
- Disable the plugin temporarily if exposure is unacceptable and no fix is available.
- Limit administrative sessions and avoid browsing untrusted content while logged in.
Validation and detection
- Confirm whether DirectoryPress is installed on each WordPress site.
- Record plugin versions and flag versions through 3.6.22 as potentially affected.
- Review WordPress admin audit logs for unexpected configuration or content changes.
- Monitor Patchstack and CVE records for corrected affected or fixed version details.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-2025-32249 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.4 (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:L
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5PatchstackVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.