WordPress

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	WordPress is a free, open-source web software and Content Management System (CMS) that offers various templates and plug-ins for users to apply to customize their website or blog. This technology is based on Hypertext Preprocessor (PHP) as the scripting/programming language for web development and My Structured Query Language (MySQL) to manage the data contained within the web application, both of which run on the web hosting service. The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g., VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e., SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITECSO
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has been assessed by the Section 508 Office and found non-conformant. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov. Please see reference tab for more information concerning product versions.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v23.1
Decision Date:	01/17/2023 at 17:42:14 UTC
Introduced By:	TRM Request
Vendor Name:	WordPress.org

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
3.3	12/12/2011
3.4	06/13/2012
3.5	12/11/2012
3.6	08/11/2013
3.7	10/24/2013
3.8	12/12/2013
3.9	04/16/2014
4.0.x	09/04/2014
4.1.x	12/18/2014
4.2.x	05/07/2015
4.3.x	08/18/2015
4.4.x	12/08/2015
4.5.x	04/12/2016
4.6.x	08/15/2016
4.7.x	12/06/2016
4.8.x	06/08/2017
4.9.x	08/02/2018
5.x	12/06/2018
6.x	11/01/2022

Current Decision Matrix (01/06/2023)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved w/Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint:The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology approved with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

<Past

CY2019

CY2020

CY2021

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

3.8

Unapproved

3.9

Unapproved

4.0.x

Unapproved

4.1.x

Unapproved

4.2.x

Unapproved

4.3.x

Unapproved

4.4.x

Unapproved

4.5.x

Unapproved

4.6.x

Unapproved

4.7.x

Unapproved

4.8.x

Unapproved

4.9.x

Approved w/Constraints
[4, 6, 8, 9, 10, 11]

Divest
[4, 6, 8, 9, 10, 11]

Divest
[4, 8, 9, 11, 12]

Unapproved

5.x

Unapproved

Approved w/Constraints
[4, 6, 8, 9, 10, 11]

Approved w/Constraints
[4, 8, 9, 11, 12]

Approved w/Constraints
[4, 8, 12, 13, 14]

Unapproved

6.x

Unapproved

Decision Constraints


[1]	Product must remain properly patched in order to mitigate known and future security vulnerabilities. Projects using this technology must meet Veterans Affair Directive 6500 and implement Federal Information Processing Standards (FIPS 199) for all laptop devices and National Institute of Standards and Technology Special Publication 800-53 for all desktop devices.

[2]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[3]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[4]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities.

[5]	This technology depends on MySQL which may only be used for Intranet applications and my not be used with PII/PHI/VA Sensitive information as of this writing. MySQL TRM constraints also apply to this product. See the MySQL TRM entry for more information.

[6]	Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities.

[7]	This technology depends on MySQL which may only be used for Intranet applications and may not be used with PII/PHI/VA Sensitive information as of this writing. MySQL TRM constraints also apply to this product. See the MySQL TRM entry for more information.

[8]	Users should check with their supervisor, Information Security Office (ISO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations.

[9]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[10]	Federal Information Processing Standards (FIPS) 140-2 devices, applications and software must be used to protect and secure VA sensitive information. Even if it leveraged FIPS 140-2 from associated devices since it is based on Hypertext Preprocessor (PHP) and MySQL it can also endanger connected FIPS 140-2 appliances through vulnerability creep. WordPress security is perpetually volatile and could possibly expose VA sensitive information inadvertently or purposefully. Due to all the plug ins and open source classification, it is recommended to implement strong continuous monitoring of code and security related patches. WordPress must only be used for non-sensitive data and comply with all listed constraints of the Initial Product Review (IPR).

[11]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[12]	Users must ensure that Microsoft Structured Query Language (SQL) Server is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) Per the Initial Product Review, users must abide by the following constraints: Federal Information Processing Standards (FIPS) 140-2 devices, applications and software must be used to protect and secure VA sensitive information. Even if it leveraged FIPS 140-2 from associated devices since it is based on Hypertext Preprocessor (PHP) and MySQL it can also endanger connected FIPS 140-2 appliances through vulnerability creep. WordPress security is perpetually volatile and could possibly expose VA sensitive information inadvertently or purposefully. Due to all the plug-ins and open source classification, it is recommended to implement strong continuous monitoring of code and security related patches. WordPress must only be used for non-sensitive data and comply with all listed constraints of the Initial Product Review (IPR).

[13]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[14]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

Note:

At the time of writing, version 6.1 is the most current version and released 11/01/2022.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description
Other	Accessibility/508 Compliance	Vendor	This website points to recommendations on how to achieve a site that follows 508 Compliance. Provides a tool web accessibility tool to test the configuration of the site to ensure that it is 100% compliant.
Best Practice	WordPress Security White Paper	Vendor	This website points to the analysis of WordPress software developments, security components, and best practices of the software.

Technology Components

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
No components have been identified for this entry.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Collaboration and Electronic Workplace Collaboration Software	Content Management

Open Source

This entry is available as an open source technology.

Operating Systems Supported by the Technology

macOS - Approved w/Constraints
Red Hat Enterprise Linux (RHEL) - Approved w/Constraints
Windows Client - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

Hypertext Transfer Protocol (HTTP)

General Analysis

Adoption Benefits

This technology is available free of charge through open source licensing and promotes VA`s open source initiative.
This application may improve productivity for specific staff whose responsibilities include customization for websites or blogs to support Section 508 compliance.
This is a well-documented technology.

Adoption Risks

This technology can potentially use My Structured Query Language (MySQL) Community Edition and Maria Database (MariaDB) Server, unapproved technologies.
This technology can potentially use File Transfer Protocol (FTP), an unapproved protocol.
The product requires MySQL version 5.6+ or MariaDB version 10.1+. MySQL and MariaDB are currently unapproved on the TRM.
The product has rapid release schedule.
The potential exists to store Personally Identifiable Information (PII), Protected Health Information (PHI) and/or VA Sensitive data and proper security standards must be followed in these cases.
WordPress is not Federal Information Processing Standards (FIPS) 140-2 certified.
WordPress as open source has shown a consistent pattern of various published vulnerabilities and instability in the older and recent versions which could jeopardize confidentiality, integrity, and availability of VA sensitive information.
There are other approved solutions that provide similar functionality available on the TRM. The use of several similar solutions may increase organization requirements for support and maintenance.
Due to the rapid release schedule of this technology, the VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.
There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see https://nvd.nist.gov/vuln/search for more details.
This product can be configured with a MySQL Commercial Edition Database, which currently has TRM constraints limiting its use to Red Hat Enterprise Linux (RHEL) only due to its many known security issues on other platforms.
The product has Software-as-a-Service (SaaS) option which is WordPress VIP Go.

Architectural Benefits

The technology is portable as it runs on multiple VA-approved operating systems.

Architectural Risks

This technology includes cloud-based functionality which has potential information security risks.

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (01/06/2023)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (01/06/2023)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES