Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Sourcing Team ApplicantPro applicantpro allows Reflected XSS.This issue affects ApplicantPro: from n/a through <= 1.3.9.
Security readout for executives and security teams
Plain-English summary
CVE-2025-23920 is a reflected cross-site scripting flaw in the WordPress ApplicantPro plugin through version 1.3.9. An attacker would need a user to interact with a crafted link or page. Successful abuse could affect confidentiality, integrity, and availability at a limited level.
Executive priority
Treat this as a high-priority WordPress plugin exposure check, especially for public recruiting or careers sites. Business urgency is driven by public web reachability and user interaction risk, not confirmed active exploitation in the provided sources.
Technical view
The issue is CWE-79 improper input neutralization during web page generation in Sourcing Team ApplicantPro for WordPress. CVSS 3.1 is 7.1: network reachable, low complexity, no privileges required, user interaction required, and scope changed. The bundle does not identify vulnerable parameters, endpoints, exploit details, or a fixed version.
Likely exposure
Exposure is most likely on public WordPress sites running the ApplicantPro plugin version 1.3.9 or earlier. The provided data does not list CPEs and does not prove exposure for sites without this plugin.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Reflected XSS generally depends on user interaction, such as convincing a victim to open attacker-controlled content. No weaponized exploit details are provided in the bundle.
Researcher notes
Evidence is limited to the CVE record and Patchstack reference. The bundle lacks endpoint, parameter, patch version, and proof-of-concept details. Validation should focus on asset inventory, version confirmation, vendor advisory review, and safe telemetry review rather than exploit reproduction.
Mitigation direction
Inventory WordPress sites for the ApplicantPro plugin and recorded versions.
Prioritize sites running ApplicantPro 1.3.9 or earlier for remediation review.
Check ApplicantPro, WordPress.org, and Patchstack guidance for a fixed version or vendor workaround.
Disable or remove the plugin where it is unused or not business-critical.
Use existing WAF and phishing controls to reduce reflected XSS delivery risk.
Validation and detection
Confirm whether ApplicantPro is installed on each WordPress property.
Verify the installed plugin version against the affected range through 1.3.9.
Review security telemetry for suspicious requests involving ApplicantPro pages or parameters.
Confirm remediation by documenting upgraded, disabled, removed, or not-installed status.
Avoid active exploit testing unless authorized and using non-destructive validation methods.
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-79: 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.
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.
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.